Skip to main content

CVE-2026-107721: CWE-613: Insufficient Session Expiration in nearform fast-jwt

0
Medium
VulnerabilityCVE-2026-107721cvecve-2026-107721cwe-613cwe-682
Published: 10/08/2026 (10/08/2026, 21:45:57 UTC)
Source: CVE Database V5
Vendor/Project: nearform
Product: fast-jwt

Description

fast-jwt before version 6.3.0 has an insufficient session expiration vulnerability due to improper handling of the clockTolerance option. Specifically, setting clockTolerance to Infinity causes the verifier to accept expired or not-yet-active JWT tokens. This occurs because infinite clock tolerance bypasses expiration (exp) and not-before (nbf) claim checks, allowing tokens to remain valid longer than intended. The issue requires administrative configuration to exploit and is fixed in version 6.3.0.

CVSS v3.1

Score 5.9medium

Attack Vector
Network
Attack Complexity
High
Privileges Required
High
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
None
CVSS:3.1/AV:N/AC:H/PR:H/UI:N/S:U/C:H/I:H/A:N

Affected software

nearform

fast-jwt

Affected versions
<6.3.0

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 10/08/2026, 22:18:50 UTC

Technical Analysis

The fast-jwt library prior to version 6.3.0 allows an application administrator to set the clockTolerance option to Infinity. The option validation checks only type and negativity but not finiteness, enabling infinite clock tolerance. This causes the validateClaimDateValue function to always pass expiration (exp) and not-before (nbf) claim comparisons, effectively accepting expired or premature tokens. Additionally, the verifier cache uses these infinite bounds, so cached entries remain valid until eviction. This vulnerability is classified under CWE-613 (Insufficient Session Expiration) and CWE-682 (Incorrect Calculation).

Potential Impact

An attacker with administrative privileges or equivalent configuration access can configure the verifier to accept expired or not-yet-active JWT tokens by setting clockTolerance to Infinity. This undermines token expiration enforcement, potentially allowing unauthorized access with tokens that should be invalid. The impact includes confidentiality and integrity compromise but requires privileged access to exploit.

Mitigation Recommendations

Upgrade fast-jwt to version 6.3.0 or later, where this issue is fixed. The fix ensures proper validation of the clockTolerance option to prevent infinite values. Until upgraded, avoid setting clockTolerance to Infinity. No other mitigations are indicated.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

Technical Details

Data Version
5.2
Assigner Short Name
GitHub_M
Date Reserved
2026-10-08T17:21:52.975Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac8135e2cdf04f6563b0ced

Added to database: 10/08/2026, 22:04:14 UTC

Last enriched: 10/08/2026, 22:18:50 UTC

Last updated: 10/08/2026, 22:19:11 UTC

Views: 7

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

Need more coverage?

Upgrade to Pro Console for AI refresh and higher limits.

For incident response and remediation, OffSeq services can help resolve threats faster.

Latest Threats

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses