CVE-2025-30144 affects the fast-jwt library prior to version 5.0.6. The library does not correctly validate the JWT iss (issuer) claim in accordance with RFC 7519, and improperly accepts an array of strings as a valid iss value. This allows an attacker to craft a token whose iss claim contains both an attacker-controlled issuer and a legitimate issuer, such as ['https://attacker-domain/', 'https://valid-iss'], and have the token pass issuer validation. In deployments where the application or related components such as JWKS retrieval/validation helpers rely on fast-jwt's issuer validation and do not independently enforce strict iss semantics, this flaw can enable acceptance of forged JWTs signed or sourced under attacker control.
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 valid public exploits. Mallory filtered out 1 candidate as fakes, detection scripts, or README-only repos.
All candidate exploits were filtered out by Mallory's validation.
4 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
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.