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-vm9r-h74p-hg97 | jose vulnerable to untrusted JWK header key acceptance during signature verification |
Mon, 06 Apr 2026 15:30:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| CPEs | cpe:2.3:a:appsup-dart:jose:*:*:*:*:*:*:*:* |
Wed, 01 Apr 2026 23:45:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
Wed, 01 Apr 2026 02:15:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Appsup-dart
Appsup-dart jose |
|
| Vendors & Products |
Appsup-dart
Appsup-dart jose |
Tue, 31 Mar 2026 16:00:00 +0000
| Type | Values Removed | Values Added |
|---|---|---|
| Description | JOSE is a Javascript Object Signing and Encryption (JOSE) library. Prior to version 0.3.5+1, a vulnerability in jose could allow an unauthenticated, remote attacker to forge valid JWS/JWT tokens by using a key embedded in the JOSE header (jwk). The vulnerability exists because key selection could treat header-provided jwk as a verification candidate even when that key was not present in the trusted key store. Since JOSE headers are untrusted input, an attacker could exploit this by creating a token payload, embedding an attacker-controlled public key in the header, and signing with the matching private key. Applications using affected versions for token verification are impacted. This issue has been patched in version 0.3.5+1. A workaround for this issue involves rejecting tokens where header jwk is present unless that jwk matches a key already present in the application's trusted key store. | |
| Title | jose vulnerable to untrusted JWK header key acceptance during signature verification | |
| Weaknesses | CWE-347 | |
| References |
| |
| Metrics |
cvssV3_1
|
Status: PUBLISHED
Assigner: GitHub_M
Published:
Updated: 2026-04-01T14:03:14.969Z
Reserved: 2026-03-26T16:22:29.034Z
Link: CVE-2026-34240
Updated: 2026-04-01T14:03:10.575Z
Status : Analyzed
Published: 2026-03-31T16:16:33.090
Modified: 2026-04-06T15:02:26.300
Link: CVE-2026-34240
No data.
OpenCVE Enrichment
Updated: 2026-04-07T08:08:01Z
Github GHSA