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-hm7r-c7qw-ghp6 | fast-jwt accepts unknown `crit` header extensions (RFC 7515 violation) |
Fri, 10 Apr 2026 18:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:nearform:fast-jwt:*:*:*:*:*:node.js:*:* |
Tue, 07 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Tue, 07 Apr 2026 00:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Nearform
Nearform fast-jwt |
|
| Vendors & Products |
Nearform
Nearform fast-jwt |
Mon, 06 Apr 2026 18:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | fast-jwt provides fast JSON Web Token (JWT) implementation. In 6.1.0 and earlier, fast-jwt does not validate the crit (Critical) Header Parameter defined in RFC 7515 §4.1.11. When a JWS token contains a crit array listing extensions that fast-jwt does not understand, the library accepts the token instead of rejecting it. This violates the MUST requirement in the RFC. | |
| Title | fast-jwt accepts unknown `crit` header extensions (RFC 7515 §4.1.11 MUST violation) | |
| Weaknesses | CWE-345 CWE-636 |
|
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-07T15:59:49.872Z
Reserved: 2026-03-31T21:06:06.428Z
Link: CVE-2026-35042
Updated: 2026-04-07T15:19:44.996Z
Status : Analyzed
Published: 2026-04-06T17:17:13.410
Modified: 2026-04-10T18:35:35.117
Link: CVE-2026-35042
No data.
OpenCVE Enrichment
Updated: 2026-04-13T14:27:45Z
Github GHSA