CVE-2026-27945 json
ZITADEL has potential SSRF via Actions
published 2026-02-26 8 mo ago modified 2026-06-17 4 mo ago also EUVD-2026-8793 , GHSA-7777-fhq9-592v , GO-2026-4574
- cvss
- 6.5
- version 3.1, NVD
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.3%
- EPSS 0.3% chance of exploitation in 30 days, percentile 17%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/zitadel/zitadel/v2 1.80.0-v2.20.0.20260225053328-b2532e966621, 4.11.1
- go github.com/zitadel/zitadel 1.80.0-v2.20.0.20260225053328-b2532e966621
- zitadel zitadel 4.11.1
- govulncheck-vulndb openSUSE Leap 15.6 0.0.20260317T205859-150000.1.152.1
suse advisories SUSE-SU-2026:1042-1
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
CISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- partial
- Assessed
- 8 mo ago
Exploit prediction
0.26% chance of exploitation in the next 30 days, higher than 17% of all scored CVEs (FIRST EPSS, 2026-11-08).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 4.0 | 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 |
| CNA | 4.0 | 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/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X |
| NVD | 3.1 | 6.5 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:L/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zitadel/zitadel/v2 | >=2.59.0, <4.11.1 <1.80.0-v2.20.0.20260225053328-b2532e966621 |
4.11.1 1.80.0-v2.20.0.20260225053328-b2532e966621 |
| go | github.com/zitadel/zitadel | <1.80.0-v2.20.0.20260225053328-b2532e966621 |
1.80.0-v2.20.0.20260225053328-b2532e966621 |
Affected products
- zitadel zitadel
Classification
- Weakness
-
- CWE-918 Server-Side Request Forgery
References
-
github.com
/zitadel/zitadel/commit/b2532e9666215bef04855d138ca716045bb74a06
web, patch
-
github.com
/zitadel/zitadel/security/advisories/GHSA-7777-fhq9-592v
web, vendor-advisory, advisory
-
github.com
/zitadel/zitadel/releases/tag/v3.4.7
release-notes
-
github.com
/zitadel/zitadel/releases/tag/v4.11.0
release-notes
-
nvd.nist.gov
/vuln/detail/CVE-2026-27945
advisory
-
github.com
/zitadel/zitadel
package
-
github.com
/zitadel/zitadel/releases/tag/v4.11.1
web
Sources
- CVE List CVE-2026-27945
- GitHub Advisory GHSA-7777-fhq9-592v
- NVD CVE-2026-27945
- OSV GO-2026-4574
Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.