Is fast-jwt affected by CVE-2026-35039?

npm fast-jwt is affected in >=0.0.1 <6.2.0.

Is CVE-2026-35039 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

critical

CVE-2026-35039

Q: Is CVE-2026-35039 being exploited?

Not on the CISA KEV list. EPSS exploit probability is 0.2%.

npm · fast-jwt

Summary

fast-jwt: Cache Confusion via cacheKeyBuilder Collisions Can Return Claims From a Different Token (Identity/Authorization Mixup)

Severity: critical
EPSS: 0.2% (p11)
Also known as: GHSA-rp9m-7r4c-75qg
Published: 2026-04-03

References

https://github.com/nearform/fast-jwt/security/advisories/GHSA-rp9m-7r4c-75qg
https://nvd.nist.gov/vuln/detail/CVE-2026-35039
https://github.com/nearform/fast-jwt/commit/de121056c6415b58770c60640881eaec67ac4ceb

Related advisories

CVE-2026-44351 — critical · npm/fast-jwt
CVE-2026-34950 — critical · npm/fast-jwt
CVE-2026-35042 — high · npm/fast-jwt
CVE-2026-35041 — medium · npm/fast-jwt
CVE-2026-35040 — medium · npm/fast-jwt

Is your project exposed to this? Stateward checks every dependency on every pull request and flags it only if your code actually reaches it.

Check my repo

Summarize with AI

ChatGPT Claude Perplexity

Sources: CISA KEV (public domain), OSV.dev & GitHub Advisory Database (CC-BY-4.0), FIRST EPSS, NVD/CWE (public domain). Served live from the Stateward advisory database.