CVE-2026-27945 ZITADEL has potential SSRF via Actions
Attackers can exploit ZITADEL Actions to perform Server-Side Request Forgery, accessing internal network services and gathering sensitive infrastructure information.
- Exploited in the wild
- Not known
- Login needed
- An administrator
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-27945?
CVE-2026-27945 is a low-severity server-side request forgery vulnerability in zitadel, published on 26 Feb 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Official description
ZITADEL is an open source identity management platform. Zitadel Action V2 (introduced as early preview in 2.59.0, beta in 3.0.0 and GA in 4.0.0) is a webhook based approach to allow developers act on API request to Zitadel and customize flows such the issue of a token. Zitadel's Action target URLs can point to local hosts, potentially allowing adversaries to gather internal network information and connect to internal services. When the URL points to a local host / IP address, an adversary might gather information about the internal network structure, the services exposed on internal hosts etc. This is sometimes called a Server-Side Request Forgery (SSRF). Zitadel Actions expect responses according to specific schemas, which reduces the threat vector. The patch in version 4.11.1 resolves the issue by checking the target URL against a denylist. By default localhost, resp. loopback IPs are denied. Note that this fix was only released on v4.x. Due to the stage (preview / beta) in which the functionality was in v2.x and v3.x, the changes that have been applied to it since then and the severity, respectively the actual thread vector, a backport to the corresponding versions was not feasible. Please check the workaround section for alternative solutions if an upgrade to v4.x is not possible. If an upgrade is not possible, prevent actions from using unintended endpoints by setting network policies or firewall rules in one's own infrastructure. Note that this is outside of the functionality provided by Zitadel.
Weakness: CWE-918
Which versions are affected by CVE-2026-27945?
5 open source packages ship an affected version, including github.com/zitadel/zitadel/v2 and github.com/zitadel/zitadel. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
github.com/zitadel/zitadel/v2 Go | All versions | 1.80.0-v2.20.0.20260225053328-b2532e966621 |
github.com/zitadel/zitadel/v2 Go | All versions | 1.80.0-v2.20.0.20260225053328-b2532e966621 |
github.com/zitadel/zitadel/v2 Go | From 2.59.0 | 4.11.1 |
github.com/zitadel/zitadel/v2 Go | From 2.59.0 | 4.11.1 |
github.com/zitadel/zitadel Go | All versions | 1.80.0-v2.20.0.20260225053328-b2532e966621 |
Products include Zitadel Zitadel.
How do I fix CVE-2026-27945?
Upgrade github.com/zitadel/zitadel/v2 to a fixed version for your release line: 1.80.0-v2.20.0.20260225053328-b2532e966621 or 4.11.1.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-27945 being exploited?
There is no known exploitation of CVE-2026-27945 in the wild and no public exploit code.
Other vulnerabilities in zitadel
- CVE-2026-29191 ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint
- CVE-2025-67494 ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login
- CVE-2025-27507 IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations
- CVE-2025-64103 Zitadel Bypass Second Authentication Factor
- CVE-2025-31123 Zitadel Expired JWT Keys Usable for Authorization Grants
Sources
Also known as GHSA-7777-fhq9-592v, GO-2026-4574.