Loading vulnerability…
CVE-2025-30204 is an asymmetric resource-consumption vulnerability in golang-jwt/jwt. Versions starting with 3.2.0 and before 4.5.2 and 5.2.2 use strings.Split in parse.ParseUnverified to split attacker-controlled JWT input on period characters. A token containing a large number of periods causes allocations proportional to input length, with an approximately 16x allocation factor, before normal JWT validation can reject the malformed token.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
58 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A vulnerability in golang-jwt/jwt (jwt-go) that permits excessive memory allocation while parsing JWT headers, creating a denial-of-service risk.
A vulnerability in golang-jwt/jwt (jwt-go) that permits excessive memory allocation during JWT header parsing.
A vulnerability in golang-jwt/jwt (jwt-go) that permits excessive memory allocation during JWT header parsing, potentially causing denial of service.
An excessive-memory-allocation vulnerability during JWT header parsing in golang-jwt/jwt (jwt-go).
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.