Skip to main content

CVE-2026-107723: CWE-1287: Improper Validation of Specified Type of Input in nearform fast-jwt

0
High
VulnerabilityCVE-2026-107723cvecve-2026-107723cwe-1287
Published: 10/08/2026 (10/08/2026, 21:51:22 UTC)
Source: CVE Database V5
Vendor/Project: nearform
Product: fast-jwt

Description

fast-jwt before version 6.3.0 improperly validates JWT payload types, allowing JSON arrays to bypass claim validations such as expiry, issuer, and audience checks. This flaw enables an attacker with a validly signed token to circumvent protections related to token claims. The issue is resolved in version 6.3.0.

CVSS v3.1

Score 8.1high

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

Affected software

nearform

fast-jwt

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

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:36 UTC

Technical Analysis

The fast-jwt library versions prior to 6.3.0 accept JWT payloads that are JSON arrays because the payload type check only verifies that the payload is an object but does not reject arrays. Consequently, claim validators that expect named properties like exp, nbf, iss, aud, sub, jti, or nonce do not find these claims in an array and skip validation silently. This allows an attacker who can produce or influence a validly signed token to bypass expiry, issuer, audience, subject, revocation, and replay protections. The opt-in requiredClaims option can enforce presence of claims to mitigate this. Signature verification remains intact and is not bypassed. The vulnerability is fixed in version 6.3.0.

Potential Impact

An attacker capable of producing or influencing a validly signed JWT can bypass critical claim validations such as expiry, issuer, audience, subject, revocation, and replay protections. This could lead to unauthorized access or token misuse despite valid signatures. The signature verification itself is not bypassed, so tokens must still be validly signed.

Mitigation Recommendations

Upgrade fast-jwt to version 6.3.0 or later, where this issue is fixed. Alternatively, enable the opt-in requiredClaims option to enforce presence of expected claims and block tokens missing them. No other mitigations are indicated by the vendor advisory.

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.976Z
Cvss Version
3.1
State
PUBLISHED

Threat ID: 6ac8135c2cdf04f6563b0c75

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

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

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

Views: 2

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