Intel

AIKIDO-2026-208205

fast-jwt is vulnerable to Insufficient Session Expiration

Insufficient Session ExpirationGHSA-687g-22h4-j4w4 Published 4 days ago

59

Medium Risk

This Affects:

JSfast-jwt
1.5.0 - 6.2.4
Fixed in 6.3.0
Are you affected? Scan for Free

TL;DR

The verifier's clockTolerance option only rejects negative numbers and does not reject a non-finite value, so configuring it as infinite disables both expiry and not-before validation. The tolerance flows into the date-claim comparisons as positive and negative infinity, making every time-based check pass unconditionally. Before the fix, expired or not-yet-active tokens are accepted as valid, and the poisoned values also corrupt the verifier's cache so affected entries stay valid until eviction. The fix requires clockTolerance to be a finite non-negative number.

Who does this affect?

You are affected if you are using a version that falls within the vulnerable range and you configure the verifier's clockTolerance option to a non-finite value such as Infinity.

Background info

fast-jwt is vulnerable to Insufficient Session Expiration in versions 1.5.0 - 6.2.4.

How to fix this

Upgrade the fast-jwt library to the patch version.