EEF-CVE-2026-75759

## Summary

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.

## Configuration

Reachable only when the OpenID Provider advertises ID token encryption (id\_token\_encryption\_alg\_values\_supported and id\_token\_encryption\_enc\_values\_supported), or, for the JARM path, authorization response encryption (authorization\_encryption\_alg\_values\_supported and authorization\_encryption\_enc\_values\_supported), and the relying party has an encryption key configured. Without those, decryption fails before the affected code is reached.