Approved changes feed: RSS · Atom
cpe:2.3:a:appsup-dart:jose:*:*:*:*:*:*:*:*
part: a version: * update: *
| Vendor | Appsup Dart (0bfc8407-4783-5700-9858-cd4fabbe6206) |
|---|---|
| Product | Jose (fee8710d-528b-5004-8007-c3923e7ee1f7) |
| Edition | * |
| Language | * |
| Software edition | * |
| Target software | * |
| Target hardware | * |
| Other | * |
| Notes | Imported from gcve-enriched-dumps CVE data |
PURL mappings
| PURL | Source | Last updated |
|---|---|---|
| No PURL mappings for this CPE yet. | ||
Vulnerability references
| Identifier | cpeApplicability | Submitted | db.gcve.eu details | Rationale |
|---|---|---|---|---|
CVE:CVE-2026-34240 |
vulnerable | 2026-06-08 07:59:11.938557 |
jose vulnerable to untrusted JWK header key acceptance during signature verification
HIGH (7.5)
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.
Published: 2026-03-31T15:44:23.578Z
Updated: 2026-04-01T14:03:14.969Z |
Imported from gcve-enriched-dumps CVE data |
Contribute
You can submit an edit proposal for this CPE entry or suggest a related product/vendor addition using the action button above.