# CVE-2026-55669: ZITADEL: Missing Token Audience Validation (`aud`) in JWT IdP Provider

> Attackers can bypass authentication in ZITADEL by using valid tokens issued for other services due to missing audience validation.

- **Severity:** Medium 4.2 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:L/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 10 Jul 2026
- **Updated:** 10 Jul 2026
- **Also known as:** GHSA-g5h5-m4hm-xjrr, GO-2026-5391

## What is CVE-2026-55669?

CVE-2026-55669 is a medium-severity authentication bypass vulnerability in zitadel, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.

### Official description

ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's external JWT Identity Provider validates a token's signature and issuer (iss) but not the audience (aud) claim, allowing a validly signed token from a trusted issuer for another relying party to be accepted by ZITADEL. This issue is fixed in versions 3.4.12 and 4.15.2.

Weakness: CWE-346 (Origin Validation Error)

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

3 open source packages ship an affected version, including github.com/zitadel/zitadel.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260615132747-d184e976fc79 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260615132747-d184e976fc79 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260615132747-d184e976fc79 |

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

Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260615132747-d184e976fc79 or later.

## Is CVE-2026-55669 being exploited?

There is no known exploitation of CVE-2026-55669 in the wild and no public exploit code.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55669 is a medium-severity authentication bypass vulnerability in zitadel, published on 10 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-55669 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260615132747-d184e976fc79
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260615132747-d184e976fc79
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260615132747-d184e976fc79

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-55669/ (Markdown: https://insights.sbomify.com/CVE-2026-55669/index.md)
```

## Sources

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

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