# CVE-2026-55671: ZITADEL: Server-Side Request Forgery (SSRF) and Denylist Bypass in Outgoing HTTP Components

> Attackers can bypass URL denylists to force the server to make requests to internal or protected endpoints via DNS rebinding or redirects.

- **Severity:** Low 2.3 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA: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:** 14 Jul 2026
- **Also known as:** GHSA-29jh-8cfq-rr8x, GO-2026-5059

## What is CVE-2026-55671?

CVE-2026-55671 is a low-severity server-side request forgery 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. From 4.0.0-rc.1 through 4.15.1, ZITADEL's HTTP notification channels, OIDC BackChannel Logout, and SAML metadata URL fetches do not consistently validate user-defined URLs against protected denylist handling, allowing server-side requests to loopback, internal IP, link-local, or redirected endpoints through DNS rebinding, redirects, or protocol downgrades. This issue is fixed in version 4.15.2.

Weakness: CWE-918 (Server-Side Request Forgery)

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

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.20260615133614-8e82ec1cb9a2 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 |
| `github.com/zitadel/zitadel` | Go | All versions | 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 |

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

Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later.

## Is CVE-2026-55671 being exploited?

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

## Fix prompt for AI coding agents

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

What it is: CVE-2026-55671 is a low-severity server-side request forgery 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-55671 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.20260615133614-8e82ec1cb9a2
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2
- github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2

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

## Sources

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

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