Advisory

GHSA-7wfc-4796-gmg5

Also known as: CVE-2025-67494, GO-2025-4210

Summary

ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Details

Summary

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.

Impact

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.

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

Patches

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:

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]](mailto:[email protected])

Credits

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

Severity

Critical Basis: The source's own band: CRITICAL

Dates

Published
2025-12-08 22:19 UTC
Modified
2025-12-15 20:25 UTC

Affected packages and fixes

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 0, fixed 1.80.0-v2.20.0.20251208091519-4c879b47334e (semver)

Fixed versions

1.80.0-v2.20.0.20251208091519-4c879b47334e

Fix

  • Fixed version 1.80.0-v2.20.0.20251208091519-4c879b47334e
    go get github.com/zitadel/[email protected]

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 1.83.4, last affected 1.87.5 (semver)

Fixed versions

None listed

Fix

No fixed version is listed.

github.com/zitadel/zitadel

Go · All systems

Affected

  • introduced 4.0.0-rc.1, fixed 4.7.1 (semver)

Fixed versions

4.7.1

Fix

github.com/zitadel/zitadel/v2

Go · All systems

Affected

  • introduced 0, fixed 1.80.0-v2.20.0.20251208091519-4c879b47334e (semver)

Fixed versions

1.80.0-v2.20.0.20251208091519-4c879b47334e

Fix

  • Fixed version 1.80.0-v2.20.0.20251208091519-4c879b47334e
    go get github.com/zitadel/zitadel/[email protected]

Fix commands are the export's own generic commands. Ojuju never runs them. Check them against your setup first.

Check your own computer: guard packages check

View this record on OSV.dev

Source

Source: GitHub Advisory Database (reviewed advisories) · CC BY 4.0

Sources & licences