CVE-2025-67494

Zitadel is vulnerable to an unauthenticated, full-read SSRF vulnerability. An unauthenticated remote attacker can force Zitadel into making HTTP requests to arbitrary domains, including internal addresses. The server then returns the upstream response to the attacker, enabling data exfiltration from internal services.

Affected Versions

Systems using the login UI (v2) and running one of the following versions are affected:

• v4.x: 4.0.0-rc.1 through 4.7.0

Workarounds

The recommended solution is to update ZITADEL to a patched version.

A ZITADEL fronting proxy can be configured to delete all x-zitadel-forward-host header values or set it to the requested host before sending requests to ZITADEL self-hosted environments.

Questions

If you have any questions or comments about this advisory, please email us at [email protected]

Credits

Thanks to Amit Laish, GE Vernova for finding and reporting the vulnerability.

ZITADEL Login UI (V2) was vulnerable to service URL manipulation through the x-zitadel-forward-host header. The service URL resolution logic treated the header as a trusted fallback for all deployments, including self-hosted instances. This allowed unauthenticated attacker to force the server to make outbound requests and read the responses, reaching internal services, exfiltrating data, and bypassing IP-based or network-segmentation controls.

Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside. Typical impact: access to internal metadata services, internal APIs, or cloud credentials.

CVE-2025-67494 has a CVSS score of 9.3 (Critical). The vector is network-reachable, no privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment. A fixed version is available (1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1); upgrading removes the vulnerable code path.

Kodem intelligence

The vulnerability has been addressed in the latest release. The patch resolves the issue by correctly validating the x-zitadel-forward-host, resp. all forwarded headers against the instance domains and trusted domains. It's no longer used to route traffic to the Zitadel API.

Before you upgrade, ensure that:

• the ZITADEL_API_URL is set and is pointing to your instance, resp. system in multi-instance deployments.
• the HTTP host (or a x-forwarded-host) is passed in your reverse proxy to the login UI.
• a x-zitadel-instance-host (or x-zitadel-forward-host) is set in your reverse for multi-instance deployments. If you're running a single instance solution, you don't need to take any actions.

Fixed versions:

• 4.x: Upgrade to >=4.7.1

1. What is CVE-2025-67494? CVE-2025-67494 is a critical-severity server-side request forgery (SSRF) vulnerability in github.com/zitadel/zitadel (go), affecting versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e. It is fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1. Untrusted input controls the target URL of a server-initiated request, which may reach internal services not otherwise accessible from outside.
2. How severe is CVE-2025-67494? CVE-2025-67494 has a CVSS score of 9.3 (Critical). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
3. Which packages are affected by CVE-2025-67494?
   • github.com/zitadel/zitadel (go) (versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e)
   • github.com/zitadel/zitadel/v2 (go) (versions < 1.80.0-v2.20.0.20251208091519-4c879b47334e)
4. Is there a fix for CVE-2025-67494? Yes. CVE-2025-67494 is fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e, 4.7.1. Upgrade to this version or later.
5. Is CVE-2025-67494 exploitable, and should I be worried? Whether CVE-2025-67494 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
6. What actually determines whether CVE-2025-67494 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
7. How do I fix CVE-2025-67494?
   • Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later
   • Upgrade github.com/zitadel/zitadel to 4.7.1 or later
   • Upgrade github.com/zitadel/zitadel/v2 to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later