CVE-2026-27945: ZITADEL has potential SSRF via Actions

Published Feb 26, 2026
·
Updated

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 3.x: Update to >=v4.11.1 or check out workarounds 2.x: Update to >=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

Credits

This vulnerability was found by zentrust partners GmbH 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.

Other sources

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.

— MITRE

Affected Software

5 affected componentsFixes available
Zitadel<4.11.1
go/github.com/zitadel/zitadel/v2<1.80.0-v2.20.0.20260225053328-b2532e966621
1.80.0-v2.20.0.20260225053328-b2532e966621
go/github.com/zitadel/zitadel/v2>=2.59.0<4.11.1
4.11.1
ZITADEL ZITADEL>=2.59.0<=3.4.6
ZITADEL ZITADEL>=4.0.0<4.11.1

Event History

Feb 26, 2026
CVE Published
via MITRE·12:29 AM
Data Sourced
via MITRE·12:29 AM
DescriptionWeakness
Data Sourced
via NVD·01:16 AM
DescriptionSeverityWeakness
Data Sourced
via NVD·01:16 AM
Affected Software
Feb 27, 2026
Advisory Published
via GitHub·09:33 PM
Data Sourced
via GitHub·09:33 PM
DescriptionWeaknessAffected Software
Dec 18, 58147
Event
via FIRST·05:48 AM

Frequently Asked Questions

1

What is the severity of CVE-2026-27945?

CVE-2026-27945 has been classified with a moderate severity due to the potential for Server-Side Request Forgery (SSRF) risks.

2

How do I fix CVE-2026-27945?

To fix CVE-2026-27945, you should upgrade to Zitadel version 4.11.1 or later.

3

Which versions of Zitadel are affected by CVE-2026-27945?

Zitadel versions from 2.59.0 up to, but not including, 4.11.1 are affected by CVE-2026-27945.

4

What impact does CVE-2026-27945 have on applications using Zitadel?

CVE-2026-27945 may allow an attacker to manipulate network requests from the server, potentially leading to sensitive data exposure.

5

Is CVE-2026-27945 specific to any particular feature of Zitadel?

Yes, CVE-2026-27945 specifically impacts the Action V2 feature used for webhook integrations in Zitadel.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203