CVE intelligence and bounded remediation
CVE-2026-27945 — ZITADEL is an open source identity management platform
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 feas…
- Severity
- Medium
- CVSS
- 6.5 (3.1)
- Published
- 2026-02-26
- CISA KEV
- Not currently listed
- Ecosystem
- software/application
- Weaknesses
- CWE-918
Affected products
- zitadel / zitadel
Matched remediation archetype
Server-side request forgery and unintended proxying
This catalog composition supplies bounded fallback guidance. Explicitly reviewed curated workflows load with the complete record below.
Check exposure
- Inventory server-side URL fetchers, webhooks, importers, previews, redirects, proxies, and protocol handlers reachable from untrusted input.
- Map egress paths to internal services, metadata endpoints, loopback, private address space, and privileged control planes.
- Review DNS resolution, redirect, proxy, credential-forwarding, and URL parsing behavior without requesting sensitive targets.
Remediate safely
- Replace arbitrary destinations with named integrations or a strict allowlist of schemes, hosts, ports, and paths.
- Resolve and validate every destination and redirect hop, then enforce egress policy independently of application checks.
- Remove ambient credentials and sensitive headers from fetchers; apply response size, time, and content limits.
Authoritative sources
Complete CVE record and remediation plan
The detailed catalog view below loads this exact record, its source evidence, and the full seven-phase agentic change plan.