fast-jwt clockTolerance: Infinity silently bypasses both exp and nbf validation (and persists in the verifier cache) (nearform fast-jwt)

CVE-2026-107721
MEDIUM 5.9

At a glance

Source
NVD
EPSS
EPSS 0.34 % · percentile 28 ()
State
PUBLISHED
Published
Updated
Assigner
GitHub_M
NVD status
Deferred

Description

fast-jwt provides fast JSON Web Token (JWT) implementation. Prior to 6.3.0, fast-jwt createVerifier accepts Infinity for clockTolerance because its option validation checks type and negativity but not finiteness. In validateClaimDateValue, infinite positive and negative modifiers make exp and nbf comparisons always pass, allowing expired or not-yet-active tokens to be accepted. The verifier cache also derives infinite bounds, so entries created under this configuration can remain valid until eviction. Exploitation requires an application administrator or equivalent configuration path to set clockTolerance to Infinity. This issue is fixed in version 6.3.0.

Weaknesses (CWE)

  • CWE-613 — DEPRECATED: Insufficient Session Expiration
  • CWE-682 — Incorrect Calculation

References

Scores

VersionScoreVectorScored by
CVSS 3.1MEDIUM 5.9CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NGitHub_M
CVSS 3.1MEDIUM 5.9CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:NNVD · security-advisories@github.com (Secondary)

Advisories

European references

Affected products

ProductVersions
nearform · fast-jwtaffected < 6.3.0

Sources

SourceLicence
CVE List (CVEProject cvelistV5)CVE Program Terms of Use
EPSS (FIRST.org)FIRST — attribution requested
ENISA EUVDENISA — reproduction authorised, source acknowledged
NVD (NIST) via fkie-cad/nvd-json-data-feedsPublic domain — this product uses data from the NVD API but is not endorsed or certified by the NVD