Skip to main content

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

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

Description

fast-jwt versions prior to 6.3.4 have an insufficient session expiration vulnerability where cached JWTs with an exp claim but no iat claim can be accepted beyond their expiration time when caching is enabled. This allows replay of previously valid tokens until the cache entry expires. The issue is fixed in version 6.3.4.

CVSS v3.1

Score 4.2medium

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

Affected software

nearform

fast-jwt

Affected versions
<6.3.4
fast-jwt
pkg:npm/fast-jwt
Affected versions
<6.3.4

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

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

Technical Analysis

The fast-jwt library's createVerifier cache mechanism incorrectly handles JWT expiration when tokens have an exp claim but lack an iat claim. Specifically, the cache expiration deadline is derived only if the iat claim is present; otherwise, the cache falls back to a default TTL. This allows the cache to return a previously valid token payload after the token's exp time without rechecking expiration, enabling replay of expired tokens until the cache entry expires. This vulnerability does not allow token forgery. The issue is resolved in fast-jwt version 6.3.4.

Potential Impact

An attacker able to replay a cached bearer token can extend access beyond the token's expiration time until the cache entry expires. This could lead to unauthorized prolonged access using expired tokens. However, the vulnerability does not permit forging tokens or elevating privileges beyond the token's original scope.

Mitigation Recommendations

Upgrade fast-jwt to version 6.3.4 or later, where this issue is fixed. No other mitigation is required as the fix addresses the root cause.

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: 6ac8135e2cdf04f6563b0ceb

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

Last enriched: 10/08/2026, 22:18:54 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