CVE Intelligence
High SSRF

CVE-2025-67494 — ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login

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.

Published Dec 9, 2025 · Updated Oct 14, 2026 · Sources: NIST National Vulnerability Database, CVE Program (cve.org) e CISA ADP, GitHub Security Advisories · CNA: GitHub_M

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

No exploitation signal in the sources consulted so far.
How the score was calculated
  • EPSS 0.4% (30-day exploitation probability)+6
  • Technical severity (high)+6
  • Automatable exploitation (SSVC)+3

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the sources call it.

Exploitation
Not confirmed
Not in CISA KEV — an absence of record, not proof it is unexploited.
EPSS FIRST
0.44%
ahead of 37% of scored CVEs · Oct 14, 2026
Affects
Zitadel
Zitadel and 2 more
CVSS base
8.6
High · 4 source(s)
Prioritization reference: 9.3 provisional

CISA SSVC assessment CISA

Three decision points CISA publishes for the CVEs it assesses (SSVC 2.0.3). A stakeholder decision, not a severity score.

Exploitation
None
none · proof-of-concept · active
Automatable
Yes
can an attacker script the kill-chain steps
Technical impact
Partial
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

  • Documented patch — github.com (NIST National Vulnerability Database)
  • Go Github.com/zitadel/zitadel: fixed in version 1.80.0-v2.20.0.20251208091519-4c879b47334e — github.com (GitHub Security Advisories)
  • Go Github.com/zitadel/zitadel: fixed in version 4.7.1 — github.com (GitHub Security Advisories)
  • Go Github.com/zitadel/zitadel/v2: fixed in version 1.80.0-v2.20.0.20251208091519-4c879b47334e — github.com (GitHub Security Advisories)

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Zitadel Zitadel, Go Github.com/zitadel/zitadel, Go Github.com/zitadel/zitadel/v2).
  2. The attack is network-based and needs no privileges: restrict exposure (ACLs, VPN, WAF) until patched.
  3. Apply the fixed version or the patch documented under Remediation.
  4. Search available logs for exploit probes matching the vulnerability class (ssrf), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Zitadel Zitadel ≥ 4.0.0 and < 4.7.1 Vulnerable NIST National Vulnerability Database
Zitadel Zitadel version < 1.80.0-v2.20.0.20251208091519-4c879b47334eversion >= 1.83.4, <= 1.87.5version >= 4.0.0-rc.1, < 4.7.1 Vulnerable CVE Program (cve.org) e CISA ADP
Go Github.com/zitadel/zitadel < 1.80.0-v2.20.0.20251208091519-4c879b47334e≥ 1.83.4 and ≤ 1.87.5≥ 4.0.0-rc.1 and < 4.7.1 Vulnerable GitHub Security Advisories
Go Github.com/zitadel/zitadel/v2 < 1.80.0-v2.20.0.20251208091519-4c879b47334e Vulnerable GitHub Security Advisories

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Attack vector
Network
Attack complexity
Low
Privileges required
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
None
Availability
None

Every base score collected

Sources score independently and may disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactScored by
9.3 CVSS 3.1 Critical 3.9 4.7 security-advisories@github.com via NIST National Vulnerability Database
9.3 CVSS 3.1 Critical — — GitHub, Inc. via GitHub Security Advisories
9.3 CVSS 3.1 Critical — — GitHub_M via CVE Program (cve.org) e CISA ADP
8.6 CVSS 3.1 High 3.9 4.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N (score shown at the top: nvd@nist.gov)
Scoring entities (NIST, CNA, ADP) score independently; each score is shown with its origin. For prioritization we use 9.3 (security-advisories@github.com via NIST National Vulnerability Database) as a conservative provisional reference — not a definitive official score.

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-918 · Server-Side Request Forgery (SSRF)

Other CVEs with this weakness →

EPSS over time FIRST

Oct 13, 2026 → Oct 14, 2026 · 2 reading(s) · max 0.44%

Detection

Read off the CVSS vector and the weakness class. Starting points, not tested rules.

  • Prioritize edge telemetry for the network-reachable component (proxy, WAF, IDS/IPS).
  • Monitor outbound requests from the server to internal IPs and cloud metadata endpoints.
web/proxy/WAF logsnetwork IDS/IPSegress traffic

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · go/github.com/zitadel/zitadel, go/github.com/zitadel/zitadel/v2
    Oct 14, 2026 · GitHub Security Advisories
  • Affected products added · zitadel/zitadel
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Record published
    Oct 13, 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • CVSS changed · 8.6
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record created in this database
    Oct 13, 2026 · NIST National Vulnerability Database
  • 2025
  • CVE published
    Dec 9, 2025 · GitHub_M

Source activity

Repeated readings are counted rather than listed.

  • 1× References added · Oct 14, 2026 – Oct 14, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

4 on the record

Elsewhere on this site

Zitadel
every CVE for this vendor
SSRF
same class
CWE-918
other pages naming this weakness

Related CVEs (same products)

  • CVE-2026-109373 ZITADEL 3.0.0 before 4.19.2 Account Takeover via Unsigned Login V2 Session Cookie 3d
  • CVE-2026-109374 ZITADEL 3.0.0 before 4.19.2 Privilege Escalation via OIDC Token Exchange Impersonation 3d
  • CVE-2026-109371 ZITADEL 3.0.0 before 4.18.0 Unauthenticated Username Change via Login V1 3d
  • CVE-2026-109372 ZITADEL 3.0.0 before 4.19.2 Account Takeover via SAML Identity-Provider Confusion 3d
  • CVE-2026-105207 ZITADEL before 4.17.3 Account Takeover via External IdP Linking 11d
  • CVE-2026-44671 ZITADEL: LDAP Filter Injection in Login Flow May 14, 2026

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.

Answered from this record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2025-67494 is "ZITADEL Vulnerable to Unauthenticated Full-Read SSRF via V2 Login", rated High. It affects Zitadel (Zitadel); versions are in the scope table. It is not in CISA KEV, which does not rule out exploitation. CVSS 8.6 describes technical severity. EPSS 0.44% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.