# 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. - **Severity:** Low 2.1 (`CVSS:4.0/AV:N/AC:L/AT:P/PR:H/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N`) - **Exploited in the wild:** Not known - **Login needed:** An administrator - **Attackable:** Over the internet - **Victim action needed:** Not needed - **Fix available:** Yes - **Published:** 26 Feb 2026 - **Updated:** 26 Feb 2026 - **Also known as:** GHSA-7777-fhq9-592v, GO-2026-4574 ## 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 (Server-Side Request Forgery) ## 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 | Ecosystem | 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: 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. ## 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](https://insights.sbomify.com/CVE-2026-29191/): ZITADEL: 1-Click Account Takeover via XSS in /saml-post Endpoint (critical 9.3) - [CVE-2025-67494](https://insights.sbomify.com/CVE-2025-67494/): ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login (critical 9.3) - [CVE-2025-27507](https://insights.sbomify.com/CVE-2025-27507/): IDOR Vulnerabilities in ZITADEL's Admin API that Primarily Impact LDAP Configurations (critical 9.0) - [CVE-2025-64103](https://insights.sbomify.com/CVE-2025-64103/): Zitadel Bypass Second Authentication Factor (high 8.7) - [CVE-2025-31123](https://insights.sbomify.com/CVE-2025-31123/): Zitadel Expired JWT Keys Usable for Authorization Grants (high 8.7) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-27945 and fix it if it is affected. What it is: 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. Exploitation: There is no known exploitation of CVE-2026-27945 in the wild and no public exploit code. Affected packages and fixed versions: - github.com/zitadel/zitadel/v2 (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260225053328-b2532e966621 - github.com/zitadel/zitadel/v2 (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260225053328-b2532e966621 - github.com/zitadel/zitadel/v2 (Go): affected from 2.59.0; fixed in 4.11.1 - github.com/zitadel/zitadel/v2 (Go): affected from 2.59.0; fixed in 4.11.1 - github.com/zitadel/zitadel (Go): affected all versions; fixed in 1.80.0-v2.20.0.20260225053328-b2532e966621 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-27945/ (Markdown: https://insights.sbomify.com/CVE-2026-27945/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-27945 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-27945 - OSV: https://osv.dev/vulnerability/CVE-2026-27945 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-27945/ Summaries are generated and may contain mistakes; the official description above is the record.