CVE-2026-107719
fast-jwt: Verifier cache accepts expired JWTs without iat.
- Medium 4.2
Description
fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.4, the fast-jwt createVerifier cache can continue accepting a previously valid, signed JWT after its exp time when caching is enabled and the token has exp but no iat. In src/verifier.js, cacheSet derives the exp cache deadline only when iat is present, so the cache falls back to cacheTTL, and a later cache hit returns the saved payload before verifyToken rechecks expiration. An attacker who can replay the same cached bearer token can extend access until the cache entry expires, but cannot forge a token through this issue. This issue is fixed in version 6.3.4.
Key facts
- Published
- 8 Oct 2026
- Last changed
- 9 Oct 2026
- Assigned by
- GitHub_M
- EPSS
- 0.272% likely to be exploited in the next 30 days, higher than 19.748% of CVEs (scores for 17 Nov 2026)
- SSVC (CISA)
- Exploitation: poc; Automatable: no; Technical impact: partial
Severity scores
Each score is shown as its source gave it. They are not averaged or merged.
- 4.2CVSS 3.1, Mediumfrom the CNA (GitHub_M)
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N
Historical context and remediation
This reference retains the original CVE publication date. A recent record update does not mean a new attack occurred.
No separately sourced impact summary is available on this page yet. Consult the description, version data and dated exploitation evidence.
No explicit remediation statement is available on this page yet. Consult the original record and vendor references before choosing a fix.
Version statuses below come from the CNA. An “unaffected” version is not necessarily a currently supported release or proof of a patch date. EPSS is a dated risk estimate, not a count of historical attacks.
Affected products
| Vendor | Product | Versions |
|---|---|---|
| nearform | fast-jwt |
|
Timeline
- 8 Oct 2026 Published