CVE-2025-302047.5HighCWE-405

CVE-2025-30204: jwt-go allows excessive memory allocation during header parsing

golang-jwt · jwt

Affected: golang-jwt jwt · Exploitation: unlikely (under 1%)

Not in CyberSIXT coverage yet: no article names this CVE. This page shows the public record.

0.8%probability of exploitation in the next 30 days

57th percentile

050100

Higher than 57% of scored CVEs

7.5HighCVSS 3.1

LowMediumHighCrit.

DescriptionCVE.org

golang-jwt is a Go implementation of JSON Web Tokens. Starting in version 3.2.0 and prior to versions 5.2.2 and 4.5.2, the function parse.ParseUnverified splits (via a call to strings.Split) its argument (which is untrusted data) on periods. As a result, in the face of a malicious request whose Authorization header consists of Bearer followed by many period characters, a call to that function incurs allocations to the tune of O(n) bytes (where n stands for the length of the function's argument), with a constant factor of about 16. This issue is fixed in 5.2.2 and 4.5.2.

Affected products1

From the CVE record. A product or version that is not listed is unknown, not unaffected.

golang-jwt · jwt>= 3.2.0, < 4.5.2; >= 5.0.0-rc.1, < 5.2.2

On the Atlas

Every published CVE is on the CyberSIXT Atlas, grouped by weakness, vendor and month.

Open the Atlas

Exploitation: Unlikely (under 1%). EPSS under 1%, or no score yet.
CISA KEV: Not listed
Public check: No public nuclei template
Weakness: Asymmetric Resource Consumption (Amplification) · Denial of Service
Published: March 2025
Band: Unlikely (under 1%), March 2025

CoverageNo articles yet

No CyberSIXT article names CVE-2025-30204 yet, so there is no coverage timeline, action brief or change log for it. Everything on this page comes from the public CVE record, CISA KEV, EPSS and the nuclei template index. Search the archive or see the CVEs in the news.