CVE-2026-75759
High 7.6No known exploitationFix availableEncrypted ID token or JARM response accepted without a nested signature in erlef oidcc
Record last updated
CVSS score
High on a 0 to 10 scale
EPSS, chance of exploitation in 30 days
Higher than 9% of scored CVEs. A prediction, not evidence.
CISA remediation deadline
Not in the KEV catalog
Description
Improper Verification of Cryptographic Signature vulnerability in erlef oidcc allows an unauthenticated attacker to impersonate an arbitrary user via an encrypted ID token or JARM response carrying no nested signature. OpenID Connect Core 1.0 section 2 requires that an encrypted ID token be signed then encrypted, with the result being a Nested JWT, and JARM processing rule 5 requires the client to check the signature unconditionally. oidcc instead accepted a JWE wrapping unsigned claims as fully validated, so anyone holding the relying party's public encryption key could mint a token with an arbitrary sub, iss, and aud without possessing the provider's signing key. In oidcc_jwt_util:verify_decrypted_token/4, a decrypted payload that is not a signed JWS fell back to parsing the plaintext claims and returning them with no verifying key. oidcc_token:int_validate_jwt/4 then matched on the JOSE structure type rather than on whether a signature had been verified, and returned success. The JARM path in oidcc_token:validate_jarm/3 is reachable through the browser front channel. UserInfo responses are not affected, because OpenID Connect Core 1.0 section 5.3.2 permits them to be encrypted without also being signed. This issue affects oidcc: from 3.2.0-beta.1 before 3.9.0.
Weakness: CWE-347
Patching and mitigation
- Patch status
- Fix available (source: CVE record (EEF))
- Fix documented (source date)
- Mitigation
- None documented
- Vendor guidance
- github.com (opens in a new tab)
Affected products
| Vendor | Product | Affected versions | Fixed in | Per |
|---|---|---|---|---|
| erlef | oidcc | from 3.2.0-beta.1 before 3.9.0 | 3.9.0 | CVE Program |
| erlef | oidcc | from 37a1361f704889816db2873f72d744d63ec39568 before 5f62fbccdae8526ff62653b8901657a6c1400fd9 | 5f62fbccdae8526ff62653b8901657a6c1400fd9 | CVE Program |
Timeline
Disclosure
CVE record published by EEF
Source: CVE Program (opens in a new tab)
Patch
Fix documented by CVE record (EEF)
Vendor guidance and references
- Fix commit 5f62fbc in erlef/oidcc (opens in a new tab)patch
- https://github.com/erlef/oidcc/security/advisories/GHSA-533g-4vf3-xwrj (opens in a new tab)related, vendor-advisory
- EEF CNA record for CVE-2026-75759 (opens in a new tab)related
- Introducing commit 37a1361 in erlef/oidcc (opens in a new tab)related
- OSV record EEF-CVE-2026-75759 (opens in a new tab)related