Your RSA-2048 keys break in 2030. Find every one of them before attackers do.
🐹 Go

CVE-2025-67494

CRITICALFix: zitadel/zitadel@4c879b4

CVE-2025-67494 is a critical-severity (CVSS 9.3) Server-Side Request Forgery (SSRF) vulnerability in github.com/zitadel/zitadel. O3 Security confirms whether CVE-2025-67494 is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

Also known asGHSA-7wfc-4796-gmg5GO-2025-4210
Published
Dec 9, 2025
Updated
Aug 8, 2026
Affected
4 pkgs
Patched
3 / 4
Exploits
None indexed

Real-World Exposure

4 pkgs affected
🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel🐹github.com/zitadel/zitadel/v2

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

ZITADEL is an open-source identity infrastructure tool. Versions 4.7.0 and below are vulnerable to an unauthenticated, full-read SSRF vulnerability. The ZITADEL Login UI (V2) treats the x-zitadel-forward-host header as a trusted fallback for all deployments, including self-hosted instances. This allows an unauthenticated attacker to force the server to make HTTP requests to arbitrary domains, such as internal addresses, and read the responses, enabling data exfiltration and bypassing network-segmentation controls. This issue is fixed in version 4.7.1.

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zitadel/zitadelall versions1.80.0-v2.20.0.20251208091519-4c879b47334e
🐹Gogithub.com/zitadel/zitadel1.83.4No fix
🐹Gogithub.com/zitadel/zitadel4.0.0-rc.1&&< 4.7.14.7.1
🐹Gogithub.com/zitadel/zitadel/v2all versions1.80.0-v2.20.0.20251208091519-4c879b47334e

Detection & mitigation playbook

Open-source dependency
  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/zitadel/zitadel. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

  2. Fix

    Update github.com/zitadel/zitadel to 1.80.0-v2.20.0.20251208091519-4c879b47334e or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms CVE-2025-67494 is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

  4. How O3 protects you

    O3 pinpoints whether CVE-2025-67494 is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to CVE-2025-67494. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

ZITADEL is an open-source identity infrastructure tool. Versions 4.7.0 and below are vulnerable to an unauthenticated, full-read SSRF vulnerability. The ZITADEL Login UI (V2) treats the x-zitadel-forward-host header as a trusted fallback for all deployments, including self-hosted instances. This allows an unauthenticated attacker to force the server to make HTTP requests to arbitrary domains, such as internal addresses, and read the responses, enabling data exfiltration and bypassing network-segmentation controls. This issue is fixed in version 4.7.1.
O3 Security · Impact-Aware SCA

Is CVE-2025-67494 in your dependencies?

O3 detects CVE-2025-67494 across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.