Analysis and contextual insights are available on OpenCVE Cloud.
No vendor fix or workaround currently provided.
Additional remediation guidance may be available on OpenCVE Cloud.
Tracking
Sign in to view the affected projects.
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-cjw9-ghj4-fwxf | fast-jwt has a ReDoS when using RegExp in allowed* leading to CPU exhaustion during token verification |
Tue, 14 Apr 2026 20:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:nearform:fast-jwt:*:*:*:*:*:node.js:*:* |
Fri, 10 Apr 2026 09:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nearform
Nearform fast-jwt |
|
| Vendors & Products |
Nearform
Nearform fast-jwt |
Thu, 09 Apr 2026 17:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Thu, 09 Apr 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | fast-jwt provides fast JSON Web Token (JWT) implementation. From 5.0.0 to 6.2.0, a denial-of-service condition exists in fast-jwt when the allowedAud verification option is configured using a regular expression. Because the aud claim is attacker-controlled and the library evaluates it against the supplied RegExp, a crafted JWT can trigger catastrophic backtracking in the JavaScript regex engine, resulting in significant CPU consumption during verification. This vulnerability is fixed in 6.2.1. | |
| Title | ReDoS in fast-jwt when using RegExp in allowed* leading to CPU exhaustion during token verification | |
| Weaknesses | CWE-1333 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-09T16:15:25.352Z
Reserved: 2026-03-31T21:06:06.428Z
Link: CVE-2026-35041
Updated: 2026-04-09T16:14:24.545Z
Status : Analyzed
Published: 2026-04-09T16:16:27.383
Modified: 2026-04-14T20:15:13.637
Link: CVE-2026-35041
No data.
OpenCVE Enrichment
Updated: 2026-04-15T16:00:07Z
Github GHSA