NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
CRITICAL severity

ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 LoginGHSA-7wfc-4796-gmg5

CRITICALFix: zitadel/zitadel@4c879b4

GHSA-7wfc-4796-gmg5 is a critical-severity (CVSS 9.3) Server-Side Request Forgery (SSRF) vulnerability in github.com/zitadel/zitadel. 1 public exploit or proof-of-concept reference is indexed, so weaponization risk is real. A fix is available for github.com/zitadel/zitadel — see the affected versions and patch details below.

Also known asCVE-2025-67494GO-2025-4210
Published
Updated
Affected
4 pkgs
Patched
3 / 4
Exploits
1 known
Exploitation data as of Nov 9, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

Exploitation Status

No confirmed exploitation observed yet

  • CISA assesses this as automatable — exploitation doesn’t require manual, per-target effort, which raises the odds of mass scanning and opportunistic attacks.
  • CISA’s own triage has not observed active exploitation or public proof-of-concept code for this CVE as of its last assessment.

Exploitation and automatability from CISA’s SSVC triage for GHSA-7wfc-4796-gmg5.

EPSS Exploitation Probability

via FIRST.org ↗
0.5%probability of exploitation in next 30 days
Lower Risk+0.03%
Lower risk than most CVEs41th percentile — riskier than 41% of all scored CVEsHighest risk
0.00%0.33%0.65%0.98%0.0%0.5%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

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

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:

  • 4.x: Upgrade to >=4.7.1

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.

Affected Packages

4 total 3 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/zitadel/zitadelall versions1.80.0-v2.20.0.20251208091519-4c879b47334ego get github.com/zitadel/zitadel@v1.80.0-v2.20.0.20251208091519-4c879b47334e
🐹Gogithub.com/zitadel/zitadel≥ 1.83.4No fix
🐹Gogithub.com/zitadel/zitadel≥ 4.0.0-rc.1&&< 4.7.14.7.1go get github.com/zitadel/zitadel@v4.7.1
🐹Gogithub.com/zitadel/zitadel/v2all versions1.80.0-v2.20.0.20251208091519-4c879b47334ego get github.com/zitadel/zitadel/v2@v1.80.0-v2.20.0.20251208091519-4c879b47334e

Affected Products

1 product · 1 configurations
Application
zitadelzitadel
≥ 4.0.0 && < 4.7.1
range
Exploits & PoCs
1

Research use only. For defensive security, authorized penetration testing, and academic research only. Never execute exploit code against systems without explicit written authorization.

Chocapikk/CVE-2025-67494

⭐ 6🍴 0Jun 2026

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, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  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 GHSA-7wfc-4796-gmg5 is resolved across your whole dependency graph.

  3. Workarounds

    Restrict outbound requests from the affected component to an allowlist of hosts, block access to link-local and internal address ranges at the network layer, and require authentication on internal services so a forged request cannot reach them unauthenticated.

Frequently Asked Questions

### 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 unaut
O3 Security · Impact-Aware SCA

Is GHSA-7wfc-4796-gmg5 in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
ZITADEL Vulnerable to Unauthenticated Full-Read SSRF…