CVE-2026-107719 MEDIUM

CVE-2026-107719: fast-jwt: Verifier cache accepts expired JWTs without iat.

Vendor Nearform
Product fast-jwt
Weakness CWE-613 · Insufficient session expiration
Published October 8, 2026
Last update October 9, 2026

CVSS base score

4.2/10
Attack vector Network
Attack complexity High
Privileges required Low
User interaction None
Confidentiality Low
Integrity Low

CVSS vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N

What the vulnerability does

01Description

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 dates

02Disclosure timeline

October 8, 2026 CVE published
October 9, 2026 Record updated