Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-35041: CWE-1333: Inefficient Regular Expression Complexity in nearform fast-jwt

0
Medium
VulnerabilityCVE-2026-35041cvecve-2026-35041cwe-1333
Published: Thu Apr 09 2026 (04/09/2026, 14:55:22 UTC)
Source: CVE Database V5
Vendor/Project: nearform
Product: fast-jwt

Description

CVE-2026-35041 is a medium severity vulnerability in nearform's fast-jwt library versions 5. 0. 0 through 6. 2. 0. It involves inefficient regular expression complexity when the allowedAud verification option is configured with a regular expression. An attacker-controlled 'aud' claim in a JWT can trigger catastrophic backtracking in the JavaScript regex engine, causing significant CPU consumption and a denial-of-service condition during token verification. This issue is fixed in version 6. 2. 1.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 04/09/2026, 16:50:50 UTC

Technical Analysis

The fast-jwt library, used for JSON Web Token implementation, contains a denial-of-service vulnerability in versions from 5.0.0 up to but not including 6.2.1. When the allowedAud verification option is set using a regular expression, the library evaluates the attacker-controlled 'aud' claim against this regex. Crafted JWTs can exploit inefficient regex evaluation leading to catastrophic backtracking and excessive CPU usage. This vulnerability is tracked as CWE-1333 and has a CVSS 3.1 base score of 4.2 (medium severity). The issue is resolved in fast-jwt version 6.2.1.

Potential Impact

Successful exploitation results in a denial-of-service condition due to high CPU consumption during JWT verification. There is no impact on confidentiality or integrity, only availability is affected. The vulnerability requires high attack complexity and privileges with user interaction, limiting its exploitability.

Mitigation Recommendations

Upgrade fast-jwt to version 6.2.1 or later where this vulnerability is fixed. Since the vendor advisory indicates the issue is resolved in 6.2.1, applying this official fix is the recommended remediation. No alternative mitigations or workarounds are provided.

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-03-31T21:06:06.428Z
Cvss Version
3.1
State
PUBLISHED
Remediation Level
null

Threat ID: 69d7d5661cc7ad14daeeafcd

Added to database: 4/9/2026, 4:35:50 PM

Last enriched: 4/9/2026, 4:50:50 PM

Last updated: 4/9/2026, 6:15:37 PM

Views: 6

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