Is CVE-2026-105214 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-105214 being exploited in the wild.

How severe is CVE-2026-105214?

Informational severity, published 4 October 2026.

Which products and versions are affected?

ZITADEL 4.0.0 through 4.16.1; 3.0.0 through 3.4.13.

How is CVE-2026-105214 attacked?

It is attacked over the network, in a hosted service.

Am I affected by CVE-2026-105214?

Check whether you run ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-105214: Zitadel server-side request forgery in domain verification

CVE-2026-105214 · Severity: info · Published 2026-10-04

Zitadel is an open-source identity and access management platform used for authentication and user management. The vulnerability allows attackers to register domains that redirect the server to internal IP addresses or cloud metadata endpoints, potentially allowing them to map internal networks, scan internal ports, or interact with unauthorized internal services. Exploitation requires an attacker to control a domain and have the ability to create an organization.

Technologies: ZITADEL. Vendors: ZITADEL.

Quick answers

Is CVE-2026-105214 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-105214 being exploited in the wild.
How severe is CVE-2026-105214?: Informational severity, published 4 October 2026.
Which products and versions are affected?: ZITADEL 4.0.0 through 4.16.1; 3.0.0 through 3.4.13.
Is there a fix for CVE-2026-105214?: Yes: fixed in Zitadel 4.16.2. Until then: If immediate upgrade to 4.16.2 is not possible, implement strict network egress firewalls or reverse proxy rules to block Zitadel from initiating outbound connections to internal networks, loopback interfaces, and cloud metadata endpoints. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-105214 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-105214?: Check whether you run ZITADEL at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

Fixed in: Zitadel 4.16.2

If immediate upgrade to 4.16.2 is not possible, implement strict network egress firewalls or reverse proxy rules to block Zitadel from initiating outbound connections to internal networks, loopback interfaces, and cloud metadata endpoints.

Technical details

A server-side request forgery (SSRF) vulnerability exists in Zitadel's organization domain HTTP verification mechanism. The vulnerability arises because domain ownership verification uses Go's default http.Get instead of the protected HTTP client with internal network denylist, DNS rebinding protection, and redirect controls. An attacker can register an organization-controlled domain that redirects to loopback, internal IP ranges (10.0.0.0/8, 172.16.0.0/12, 192.168.0.0/16), or cloud metadata endpoints (169.254.169.254), allowing network reconnaissance and potential access to internal services.

Affected products

Zitadel Zitadel 4.0.0 through 4.16.1; 3.0.0 through 3.4.13

Timeline

2026-07-29: disclosed
2026-10-04: advisory

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.