# CVE-2026-75759: Encrypted ID token or JARM response accepted without a nested signature in erlef oidcc

> An attacker can impersonate any user by sending an encrypted but unsigned ID token or JARM response, bypassing signature verification in the oidcc library.

- **Severity:** High 7.6 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** A user has to click or open something
- **Fix available:** Yes
- **Published:** 30 Aug 2026
- **Updated:** 31 Aug 2026
- **Also known as:** EEF-CVE-2026-75759, GHSA-533g-4vf3-xwrj

## What is CVE-2026-75759?

CVE-2026-75759 is a high-severity authentication bypass vulnerability in erlef oidcc, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.

### Official 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 (Improper Verification of Cryptographic Signature)

## Which versions are affected by CVE-2026-75759?

1 open source package ship an affected version, including oidcc.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `oidcc` | Hex | From 3.2.0-beta.1 | 3.9.0 |

## How do I fix CVE-2026-75759?

Upgrade oidcc to 3.9.0 or later.

## Is CVE-2026-75759 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75759 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-75759 and fix it if it is affected.

What it is: CVE-2026-75759 is a high-severity authentication bypass vulnerability in erlef oidcc, published on 30 Aug 2026. An attacker can exploit it over the internet without logging in, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-75759 exists.

Affected packages and fixed versions:
- oidcc (Hex): affected from 3.2.0-beta.1; fixed in 3.9.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-75759/ (Markdown: https://insights.sbomify.com/CVE-2026-75759/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-75759
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-75759
- OSV: https://osv.dev/vulnerability/CVE-2026-75759

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-75759/
Summaries are generated and may contain mistakes; the official description above is the record.