ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login
CVE-2025-67494GHSA-7wfc-4796-gmg5
What to do
Partial vendor fix. Follow the primary source's mitigation guidance and check back for a fix.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
- Affected
- < 1.80.0-v2.20.0.20251208091519-4c879b47334e>= 1.83.4, <= 1.87.5>= 4.0.0-rc.1, < 4.7.1
- Fixed in
- 4.7.1, 1.80.0-v2.20.0.20251208091519-4c879b47334e
Go github.com/zitadel/zitadel/v2
- Affected
- < 1.80.0-v2.20.0.20251208091519-4c879b47334e
- Fixed in
- 1.80.0-v2.20.0.20251208091519-4c879b47334e
Sources
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-7wfc-4796-gmg5 lists affected ranges: Go github.com/zitadel/zitadel >=0 =1.83.4 =4.0.0-rc.1 =0 <1.80.0-v2.20.0.20251208091519-4c879b47334e
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 9.3 · CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:L/A:N
- EPSS
- CVE-2025-67494: 0.44% estimated exploitation activity in the next 30 days; percentile 38.64 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
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…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 1 · created ·
Published from ghsa record GHSA-7wfc-4796-gmg5
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2025-67494 Advisory: ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login IDs: CVE-2025-67494, GHSA-7wfc-4796-gmg5 Record: https://patchnext.com/advisories/cve-2025-67494 (revision 1, source checked 26 Oct 2026, 15:13 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Partial vendor fix; fixed versions by package: github.com/zitadel/zitadel 4.7.1, 1.80.0-v2.20.0.20251208091519-4c879b47334e; github.com/zitadel/zitadel/v2 1.80.0-v2.20.0.20251208091519-4c879b47334e. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/zitadel/zitadel: affected < 1.80.0-v2.20.0.20251208091519-4c879b47334e; >= 1.83.4, <= 1.87.5; >= 4.0.0-rc.1, < 4.7.1; fixed in 4.7.1, 1.80.0-v2.20.0.20251208091519-4c879b47334e - Go github.com/zitadel/zitadel/v2: affected < 1.80.0-v2.20.0.20251208091519-4c879b47334e; fixed in 1.80.0-v2.20.0.20251208091519-4c879b47334e ## Suggested inspection (read-only) - Go github.com/zitadel/zitadel: check the installed version with your package manager. - Go github.com/zitadel/zitadel/v2: check the installed version with your package manager. ## Supported action No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/zitadel/zitadel, github.com/zitadel/zitadel/v2. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://github.com/advisories/GHSA-7wfc-4796-gmg5 (GitHub-reviewed advisory GHSA-7wfc-4796-gmg5 lists affected ranges: Go github.com/zitadel/zitadel >=0 =1.83.4 =4.0.0-rc.1 =0 <1.80.0-v2.20.0.20251208091519-4c879b47334e) Commands are suggestions: review each one before running it.
Loading voting…