fast-jwt accepted expired tokens from its verifier cache when the JWT carried no iat claim
- Sources: advisory
- Summary: On fast-jwt versions up to 6.3.3 with caching enabled, a token carrying
expbut noiatstays accepted from the verifier cache for the fullcacheTTL, which defaults to 10 minutes. The flaw is tracked as CVE-2026-107719 and fixed in 6.3.4. - Why it matters: With caching enabled, a token holding exp but no iat stays accepted for the full cacheTTL, 10 minutes by default, after it expires, so expiry stops bounding a stolen bearer token on versions up to 6.3.3.