CVE-2026-27945: Github.com/zitadel/zitadel/v2 ZITADEL Has Potential SSRF Vulnerability

LOW
Advisory Identifier: GHSA-7777-fhq9-592v
CWE-918
Published
Advisory Summary

CVE-2026-27945 is a LOW zitadel has potential ssrf vulnerability (CWE-918: Server-Side Request Forgery (SSRF)) affecting Github.com/zitadel/zitadel/v2 libraries in the Go ecosystem. The issue involves zitadel has potential ssrf via actions. Remediation is available by upgrading affected packages to version 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621.

CVE-2026-27945 at a Glance

CVE Identifier CVE-2026-27945
GHSA Identifier GHSA-7777-fhq9-592v
Severity LOW
CVSS v3.1 Base Score N/A
CWE Classification CWE-918: Server-Side Request Forgery (SSRF)
Affected Product Github.com/zitadel/zitadel/v2
Package Ecosystem Go
Published Date
Last Updated

How to Fix CVE-2026-27945

To remediate this vulnerability, upgrade all affected Github.com/zitadel/zitadel/v2 dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/zitadel/zitadel/v2 fixed: 4.11.1
Upgrade github.com/zitadel/zitadel/v2 to 4.11.1
github.com/zitadel/zitadel/v2 fixed: 1.80.0-v2.20.0.20260225053328-b2532e966621
Upgrade github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20260225053328-b2532e966621
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/zitadel/zitadel/v2

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-27945, inspect your project dependencies for Github.com/zitadel/zitadel/v2:

inspect dependencies for github.com/zitadel/zitadel/v2

Analyze the terminal output to locate any version of Github.com/zitadel/zitadel/v2 in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 4.11.1), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-918: Server-Side Request Forgery (SSRF), where the web server receives a url or similar request from an upstream component and retrieves the contents of this url, but it does not sufficiently ensure that the request is being sent to the expected destination. In Github.com/zitadel/zitadel/v2, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### Summary 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. ### Impact 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. ### Affected Versions Systems running one of the following versions are affected: - **4.x**: `4.0.0` through `4.11.0` (including RC version) - **3.x**: `3.0.0` to `3.4.6` (including RC versions) - **2.x**: `2.59.0` to `2.71.19` ### Patches The vulnerability has been addressed in the latest releases. The patch 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. 4.x: Upgrade to >=[4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1) 3.x: Update to >=[v4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1) or check out workarounds 2.x: Update to >=[v4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1) or check out workarounds ### Workarounds The recommended solution is to update Zitadel to a patched version. If an upgrade is not possible, users can prevent actions from using unintended endpoints by setting network policies or firewall rules in your infrastructure. Note that this is outside of the functionality provided by ZITADEL. ### Questions If there are any questions or comments about this advisory, please send an email to [security@zitadel.com](mailto:security@zitadel.com) ### Credits This vulnerability was found by [zentrust partners GmbH](https://zentrust.partners) during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann. The full report will be made public after the complete review.

CVE-2026-27945 Affected Github.com/zitadel/zitadel/v2 Versions

2 component(s)
Fixed Versions:
4.11.11.80.0-v2.20.0.20260225053328-b2532e966621
Product / Package Ecosystem Affected Versions Fixed Version
github.com/zitadel/zitadel/v2
Go
≥ 2.59.0
< 4.11.1
4.11.1
github.com/zitadel/zitadel/v2
Go
< 1.80.0-v2.20.0.20260225053328-b2532e966621
1.80.0-v2.20.0.20260225053328-b2532e966621

References

Frequently Asked Questions

What is CVE-2026-27945?
CVE-2026-27945 is a security vulnerability in Github.com/zitadel/zitadel/v2 involving ZITADEL has potential SSRF via Actions under CWE-918: Server-Side Request Forgery (SSRF).
Which Github.com/zitadel/zitadel/v2 versions are affected?
Affected versions include releases prior to 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621 across affected packages: github.com/zitadel/zitadel/v2.
What version fixes CVE-2026-27945?
Upgrading to 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/zitadel/zitadel/v2 affected?
Yes, github.com/zitadel/zitadel/v2 is affected in releases prior to 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621. Upgrade your dependency to 4.11.1, 1.80.0-v2.20.0.20260225053328-b2532e966621 or later.
What CWE is associated with CVE-2026-27945?
CVE-2026-27945 is classified under CWE-918: Server-Side Request Forgery (SSRF) (The web server receives a URL or similar request from an upstream component and retrieves the contents of this URL, but it does not sufficiently ensure that the request is being sent to the expected destination.).
How can I check Go dependencies for CVE-2026-27945?
Run the dependency tree command: 'inspect dependencies for github.com/zitadel/zitadel/v2'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-7777-fhq9-592v",
  "modified" : "2026-02-27T21:33:54Z",
  "published" : "2026-02-27T21:33:54Z",
  "aliases" : [ "CVE-2026-27945" ],
  "summary" : "ZITADEL has potential SSRF via Actions",
  "details" : "### Summary\n\nZITADEL 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.\n\nZITADEL's Action target URLs can point to local hosts, potentially allowing adversaries to gather internal network information and connect to internal services.\n\n### Impact\n\nWhen 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).\n\nZITADEL Actions expect responses according to specific schemas, which reduces the threat vector.\n\n### Affected Versions\n\nSystems running one of the following versions are affected:\n- **4.x**: `4.0.0` through `4.11.0` (including RC version)\n- **3.x**: `3.0.0` to `3.4.6` (including RC versions)\n- **2.x**: `2.59.0` to `2.71.19`\n\n### Patches\n\nThe vulnerability has been addressed in the latest releases. The patch resolves the issue by checking the target URL against a denylist. By default localhost, resp. loopback IPs are denied.\n\nNote 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.\n\n4.x: Upgrade to >=[4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1)\n3.x: Update to >=[v4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1) or check out workarounds\n2.x: Update to >=[v4.11.1](https://github.com/zitadel/zitadel/releases/tag/v4.11.1) or check out workarounds\n\n### Workarounds\n\nThe recommended solution is to update Zitadel to a patched version.\n\nIf an upgrade is not possible, users can prevent actions from using unintended endpoints by setting network policies or firewall rules in your infrastructure. Note that this is outside of the functionality provided by ZITADEL.\n\n### Questions\n\nIf there are any questions or comments about this advisory, please send an email to [security@zitadel.com](mailto:security@zitadel.com)\n\n### Credits\n\nThis vulnerability was found by [zentrust partners GmbH](https://zentrust.partners) during a scheduled penetration test. Thank you to the analysts Martin Tschirsich, Joud Zakharia, Christopher Baumann.\nThe full report will be made public after the complete review.",
  "severity" : [ {
    "type" : "CVSS_V4",
    "score" : "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"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "2.59.0"
      }, {
        "fixed" : "4.11.1"
      } ]
    } ]
  }, {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/zitadel/zitadel/v2"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.80.0-v2.20.0.20260225053328-b2532e966621"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/security/advisories/GHSA-7777-fhq9-592v"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-27945"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/commit/b2532e9666215bef04855d138ca716045bb74a06"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/zitadel/zitadel"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/zitadel/zitadel/releases/tag/v4.11.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-918" ],
    "severity" : "LOW",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-02-27T21:33:54Z",
    "nvd_published_at" : "2026-02-26T01:16:25Z"
  }
}