A vulnerability in jose versions up to and including 0.3.5 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.
Upgrade to 0.3.5+1 or later.
Reject tokens where header jwk is present unless that jwk matches a key already present in the application's trusted key store.
Fix commit: fix: improved key resolution in JsonWebKeyStore
{
"github_reviewed": true,
"github_reviewed_at": "2026-03-31T23:09:16Z",
"severity": "HIGH",
"nvd_published_at": "2026-03-31T16:16:33Z",
"cwe_ids": [
"CWE-347"
]
}