Is CVE-2026-55671 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-55671 being exploited in the wild.

How severe is CVE-2026-55671?

Medium severity, with a CVSS score of 4, published 10 July 2026.

Which products and versions are affected?

github.com/zitadel/zitadel (Go) < 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2, SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2; ZITADEL 3.0.0 - 3.4.11, 4.0.0 - 4.15.1, 4.0.0-rc.1 through 4.15.1; 3.0.0 through 3.4.11.

Is there a fix for CVE-2026-55671?

Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-55671 attacked?

It is attacked over the network, in a network appliance.

Am I affected by CVE-2026-55671?

Check whether you run github.com/zitadel/zitadel (Go) or ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55671: ZITADEL SSRF and denylist bypass in outgoing HTTP components

Q: Is there a fix for CVE-2026-55671?

Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-55671 attacked?

It is attacked over the network, in a network appliance.

Q: Am I affected by CVE-2026-55671?

Check whether you run github.com/zitadel/zitadel (Go) or ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-55671 · Severity: medium · CVSS 4 · Published 2026-07-10

ZITADEL, an open-source identity management platform, is vulnerable to a security flaw where certain features—such as notification webhooks and logout processes—can be manipulated to send unauthorized requests to internal systems. An attacker with low-level access could use this to probe the organization's internal network, scan for open ports, or interact with sensitive internal services that are not intended to be public. This could lead to the exposure of internal network architecture or unauthorized access to internal infrastructure.

Technologies: github.com/zitadel/zitadel (Go), ZITADEL. Vendors: Go, ZITADEL.

Quick answers

Is CVE-2026-55671 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-55671 being exploited in the wild.
How severe is CVE-2026-55671?: Medium severity, with a CVSS score of 4, published 10 July 2026.
Which products and versions are affected?: github.com/zitadel/zitadel (Go) < 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2, SEMVER:introduced=0,fixed=1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2; ZITADEL 3.0.0 - 3.4.11, 4.0.0 - 4.15.1, 4.0.0-rc.1 through 4.15.1; 3.0.0 through 3.4.11.
Is there a fix for CVE-2026-55671?: Yes. github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-55671 attacked?: It is attacked over the network, in a network appliance.
Am I affected by CVE-2026-55671?: Check whether you run github.com/zitadel/zitadel (Go) or ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/zitadel/zitadel (Go): upgrade to 1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2 or later
```
go get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20260615133614-8e82ec1cb9a2
```

Technical details

A Server-Side Request Forgery (SSRF) vulnerability exists in ZITADEL's outgoing HTTP components, specifically within HTTP notification channels, OIDC BackChannel Logout, and SAML metadata URL fetches. The application fails to consistently validate user-supplied URLs against a protected denylist, and the existing denylist mechanism was found to be bypassable via DNS rebinding, HTTP redirects, and protocol downgrades (HTTPS to HTTP). An authenticated attacker with low privileges can provide malicious URLs pointing to loopback addresses, internal IP ranges, or cloud metadata services (IMDS). This allows for internal network mapping and interaction with unauthorized internal services. The fix, introduced in version 4.15.2, implements a hardened HTTP client with DNS rebinding protection and a unified denylist.

Affected products

ZITADEL ZITADEL 4.0.0-rc.1 through 4.15.1; 3.0.0 through 3.4.11

Identifiers

CVE-2026-55671
GHSA-29jh-8cfq-rr8x
GO-2026-5059

Timeline

2026-06-15: patched: Fix committed to repository
2026-06-17: advisory: GitHub Security Advisory published and version 4.15.2 released
2026-07-10: disclosed: CVE published to NVD

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.