CVE-2026-105214: Zitadel before 4.16.2 contains a server-side request forgery vulnerability that allows attackers to make the server request internal resources
Affects zitadelSource GCVE Database
Not known to be exploited · CVSS 2.3 Low : upgrade to 4.16.2 when convenient.
Data as of 18 Nov 2026, 20:25 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 12% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
- Patch
- Available – fixed in 4.16.2
CVSS:4.0/AV:N/AC:L/AT:P/PR:L/UI:N/VC:L/VI:L/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:XExploitation evidence
Disclosed: evidence found.
CVE published 4 Oct 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 18 Nov 2026.
What to do
Upgrade zitadel/zitadel to 4.16.2.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
GitHubzitadel/zitadelpkg:github/zitadel/zitadelOther threats | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in Zitadel version 4.16.2. Users should upgrade to version 4.16.2 or later to remediate this SSRF vulnerability. No other mitigation guidance is provided or required.
Description
Zitadel versions prior to 4.16.2 contain a server-side request forgery (SSRF) vulnerability. This flaw allows attackers to exploit the organization domain HTTP verification process to make the server request internal resources. The vulnerability arises because the challenge fetch uses Go's default http.Get method instead of a protected client, enabling attackers to register domains that redirect to loopback, internal, or cloud metadata addresses. This can be used to scan ports and map internal networks.