Critical severity · published Apr 6, 2026
CVE-2026-35039
fast-jwt Affected by Cache Confusion via cacheKeyBuilder Collisions Can Return Claims From a Different Token (Identity/Authorization Mixup)
9.1
CVSS
0.2%
EPSS
No
On KEV
Description
fast-jwt provides fast JSON Web Token (JWT) implementation. From 0.0.1 to before 6.2.0, setting up a custom cacheKeyBuilder method which does not properly create unique keys for different tokens can lead to cache collisions. This could cause tokens to be mis-identified during the verification process leading to valid tokens returning claims from different valid tokens and users being mis-identified as other users based on the wrong token. Version 6.2.0 contains a patch.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Confidentiality
High
Integrity
High
Availability
None
Scope
Unchanged
Exploitation
Is it being used?
Exploit prediction (EPSS)0.2% · higher than 12% of CVEs
Exploited in the wildNo evidence yet
CISA KEVNot listed
Ransomware campaign useNot known
Affected products
Which versions
FA
fast-jwt · nearform
>= 0.0.1, < 6.2.0 · source: vendor, NVD
Affected product
FA
fast-jwt
nearform
More from fast-jwt
9.8
CVE-2026-107722
fast-jwt: Incomplete patch of CVE-2026-34950: Non-whitespace key-prefix re-enables RSA→HS256 algorithm confusion
9.1
CVE-2026-44351
fast-jwt: Empty HMAC secret accepted via async key resolver - JWT auth bypass
9.1
CVE-2026-34950
fast-jwt has an incomplete fix for CVE-2023-48223: JWT Algorithm Confusion via Whitespace-Prefixed RSA Public Key
8.1
CVE-2026-107723
fast-jwt : Silent claim-validator bypass when JWT payload is a JSON array
7.5
CVE-2026-35042
fast-jwt accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation)