CVE-2026-35039
Nearform Fast-jwt vulnerability
- Published6 Apr 2026
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 3.1 breakdown
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NAffected products
Remediation
References
Related CVEs
Recent high-severity vulnerabilities sharing a weakness type.
Frequently asked
Is CVE-2026-35039 being actively exploited?
CVE-2026-35039 is not in the CISA KEV catalog. Its EPSS exploit probability is 0.22%.
How severe is CVE-2026-35039?
CVE-2026-35039 has a CVSS 3.1 base score of 9.1, rated critical. EPSS estimates a 0.22% probability of exploitation.
Which products are affected by CVE-2026-35039?
Affected products include Nearform Fast-jwt.
How do I fix CVE-2026-35039?
Upgrade affected software to a fixed version, for example Nearform Fast-jwt 6.1.0 or later, then confirm no affected versions remain in your inventory.
How Secuno handles this
Secuno correlates vulnerabilities like CVE-2026-35039 against the real software inventory on every managed device, every day. Rather than a static severity, each match is scored in context: exploit availability, EPSS, the asset's exposure, and business criticality decide where it lands in the queue. If an affected version is present anywhere across your portfolio, it surfaces automatically with a prioritised remediation path.
Data from the NVD, CISA KEV catalog and FIRST EPSS. CVSS 3.1 base score shown where available.