Skip to main content

ZITADEL EUVDEUVD-2026-97670

| CVE-2026-109372 CRITICAL
Improper Authentication (CWE-287)
2026-10-12 VulnCheck GHSA-65fv-6pff-4q47
9.3
CVSS 4.0 · Vendor: VulnCheck
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Authenticate as organization administrator
  2. Delivery
    Register SAML provider with attacker signing key
  3. Exploit
    Craft intent callback naming victim's linked provider
  4. Execution
    Forge assertion signed with attacker key
  5. Impact
    Obtain authenticated session as targeted cross-org user

Vulnerability Assessment

Weakness
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Authentication mechanism validation
MITRE ATT&CK

2 techniques across 2 tactics: Defense Evasion, Initial Access

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Requires the attacker to already hold organization-administrator permission on the target ZITADEL instance (PR:H) and the ability to register a new SAML identity provider with a signing key of their choosing. A viable target user must be linked to a different, legitimate SAML provider on the same instance - the bypass works because the intent callback verifies the assertion signature against the provider named in the request URL but resolves the user from the login intent without confirming the two match. Exploitation is limited by the org-admin prerequisite and by the requirement that victims authenticate via SAML identity providers; instances that do not use SAML federation or that tightly restrict org-admin assignment are not realistically exposed. No special network positioning or user interaction is needed (AV:N/UI:N).

Impact

This is a genuine high-priority vulnerability, though not a 'spray-and-pray' internet-wide threat. The CVSS 4.0 vector (CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N, score 9.3) tells a consistent story with the description: network-reachable, low attack complexity, no user interaction, but requiring high privileges (PR:H) - the attacker must already hold organization-administrator permission on the ZITADEL instance. The high-privilege requirement is the single most important mitigating signal and explains why this is a privilege-escalation/account-takeover flaw rather than an unauthenticated breach. Where it becomes severe is the scope change (SC:H/SI:H) and VC:H/VI:H: a compromised or malicious org-admin in one tenant can mint sessions as any user linked to another SAML provider on the instance, INCLUDING users in other organizations, which breaks the core tenant-isolation guarantee of a multi-tenant IAM product. No EPSS score, KEV listing, or public POC was provided in the input, so exploitation probability cannot be quantified; absence of a POC does not imply difficulty given AC:L. The CVSS vector and the prose description agree (both point to authenticated/network with a trust-boundary cross), so there is no internal conflict to flag - but defenders should note the risk is concentrated in environments that delegate org-admin to semi-trusted or numerous parties.

Exploit ScenarioDerived

An attacker who holds organization-administrator rights in one tenant of a shared ZITADEL instance registers a SAML identity provider configured with their own signing key. They then drive the SAML intent callback so the assertion is validated against their attacker-controlled provider while the login intent resolves to a victim user bound to a different, legitimate SAML provider - yielding an authenticated session as that victim, potentially in another organization. No public exploit code was identified at time of analysis, but the low attack complexity (AC:L) and absence of required user interaction make exploitation straightforward for anyone meeting the org-admin prerequisite.

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.4% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 12, 2026

Authentication bypass in ZITADEL 4.x before 4.19.2 and 3.x through 3.4.15 lets an authenticated attacker with organization-administrator permission register a SAML identity provider using their own signing key and then obtain authenticated sessions as any user linked to a different SAML provider on the same instance, including users in other organizations. The flaw stems from the SAML identity-provider intent callback verifying the assertion signature against the provider named in the request URL while resolving the user from the login intent without confirming the two match. This is a genuine high-priority vulnerability, though not a 'spray-and-pray' internet-wide threat; exploitation requires the org-admin prerequisite and that victims authenticate via SAML identity providers. No public exploit identified at time of analysis, and a vendor-released patch exists (4.19.2 and later for 4.x; a fix beyond 3.4.15 for 3.x).

RemediationAI

Upgrade to ZITADEL 4.19.2 or later for the 4.x branch, and to a version later than 3.4.15 (e.g., 3.4.16) for the 3.x branch, as directed by the vendor advisory (https://github.com/zitadel/zitadel/security/advisories/GHSA-x4c7-fpcx-w9q6). If immediate patching is not possible, reduce exposure by strictly limiting the organization-administrator role to trusted personnel, as the attacker must already hold that permission; note that this may impede legitimate administration. Additionally, if SAML federation is not essential, consider disabling it entirely-though this breaks federated logins. Audit existing SAML identity providers and remove any that are unrecognized or have unexpected signing keys. Enforce monitoring for new SAML provider registrations and for anomalous authentication events, particularly those crossing organization boundaries. These compensating controls are not complete substitutes for patching because they only raise the bar for exploitation and may introduce operational trade-offs.

Affected VersionsENISA

zitadel 3.0.0 <4.19.2

Affected Packages

euvd zitadel fix: 4.19.2

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 1 package in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

ZITADEL is an open-source identity and access management platform that supports SAML federation. The vulnerability (CWE-287: Improper Authentication) arises in the SAML identity-provider intent callback. When a SAML response is received, the callback verifies the assertion signature using the public key of the identity provider specified in the request URL. However, it then resolves the authenticating user from the stored login intent without checking that the intent's associated provider matches the provider used for signature verification. An attacker who can create a new SAML identity provider (requiring organization-administrator permission) can supply a provider with their own signing key, craft a signed assertion for a victim user, and cause the callback to treat the victim as authenticated-even though the victim is legitimately linked to a different SAML provider. The CPE cpe:2.3:a:zitadel:zitadel:*:*:*:*:*:*:*:* confirms ZITADEL as the affected product; the vulnerability affects the 4.x branch before 4.19.2 and the 3.x branch through 3.4.15. The assessed CVSS:3.1 vector (AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N) reflects that exploitation requires high privileges, no user interaction, and results in cross-scope confidentiality and integrity impact, with availability unaffected.

Know when Zitadel gets its next vulnerability

  • Watch products and get an email when something new is published
  • Check this CVE against your own stack and servers
  • Exploit and PoC references, threat intelligence from 22 sources

No credit card · 7-day full trial

Severity by source

Vendor (VulnCheck) PRIMARY 9.3 CRITICAL
CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N
vuln.today AI 8.7 HIGH

Org-admin is required so PR:H; network-reachable callback with no user interaction gives AV:N/AC:L/UI:N; cross-organization impersonation crosses a trust boundary so S:C with high confidentiality and integrity impact and no availability effect.

3.1 AV:N/AC:L/PR:H/UI:N/S:C/C:H/I:H/A:N
4.0 AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:N/SC:H/SI:H/SA:N

Primary rating from Vendor (VulnCheck).

CVSS VectorVendor: VulnCheck

Attack Vector
Network
Attack Complexity
Low
Attack Requirements
None
Privileges Required
High
User Interaction
None
Vulnerable system: Confidentiality
High
Vulnerable system: Integrity
High
Vulnerable system: Availability
None
Subsequent system: Confidentiality
High
Subsequent system: Integrity
High
Subsequent system: Availability
None

Lifecycle Timeline

2
Patch available
Oct 12, 2026 - 18:03 EUVD
CVE Published
Oct 12, 2026 - 16:05 cve.org
CRITICAL 9.3

DescriptionCVE.org

ZITADEL 4.x before 4.19.2 and 3.x through 3.4.15 contains an authentication bypass in the SAML identity-provider intent callback, which verifies the assertion signature using the provider named in the request URL but resolves the user from the login intent without checking they match. Attackers with organization-administrator permission can register a SAML provider with their own signing key to obtain authenticated sessions as any user linked to another SAML provider on the instance, including in other organizations.

Technical POC Analysis

The advisory describes CWE-287 Improper Authentication in ZITADEL's SAML identity-provider intent callback, the endpoint used by Login V2 and custom login UIs on the session API to complete an extern…

Full technical POC analysis - root cause, step-by-step exploitation and patch breakdown - is part of the Pro and Business plans.

Executive ViewAI

Why It Matters

ZITADEL versions 4.x before 4.19.2 and 3.x through 3.4.15 contain a critical authentication bypass that allows an attacker with organization-administrator privileges to register a SAML identity provider with their own signing key and then impersonate any user linked to a different SAML provider, including users in other organizations. This undermines the integrity of federated identity across the organization and could lead to unauthorized access to sensitive applications and data. Leadership should prioritize remediation given the critical severity and potential cross-organizational impact.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.4%
Top 71% exploitable
Prevalence
Medium
popular open-source cloud-native IAM, moderate and growing adoption
Data Quality
5 sources
Confidence: Medium

How this decision was reached

The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.

SignalValue
Severity CRITICAL
CISA KEV No
Public POC No
EPSS 0.4%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation· derived
None
System Exposure· derived
Open
Automatable· derived
No
Human Impact
Very High

Priority Score

46
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +46
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Authentication bypass attacks exploit flaws in the verification mechanisms that control access to systems and applications.

CVE-2024-49753 CRITICAL POC
9.1 Oct 25

Zitadel is open-source identity infrastructure software. Rated critical severity (CVSS 9.1), this vulnerability is remot

CVE-2023-49097 HIGH POC
8.8 Nov 30

ZITADEL is an identity infrastructure system. Rated high severity (CVSS 8.8), this vulnerability is remotely exploitable

CVE-2026-105207 CRITICAL
9.3 Oct 04

Account takeover in ZITADEL affects instances running 3.0.0 through 3.4.15 and 4.0.0 before 4.17.3: an unauthenticated r

CVE-2026-105209 CRITICAL
9.3 Oct 04

Cross-organization account takeover in ZITADEL 3.x before 3.4.15 and 4.x before 4.17.1 allows an authenticated attacker

CVE-2026-29191 CRITICAL
9.3 Mar 07

Stored XSS in ZITADEL identity management platform versions 4.0.0 to 4.11.1 allows unauthenticated attackers to inject p

CVE-2026-105215 CRITICAL
9.3 Oct 04

Account pre-hijacking in ZITADEL lets an unauthenticated remote attacker create a user record already bound to a victim'

CVE-2026-109373 CRITICAL
9.2 Oct 12

Authentication bypass in ZITADEL's Login V2 UI (versions 3.0.0 through 4.19.1) allows unauthenticated attackers to take

CVE-2026-105211 CRITICAL
9.2 Oct 04

Remote account takeover in ZITADEL versions before 4.17.1 allows unauthenticated attackers to compromise MFA-protected a

CVE-2025-27507 CRITICAL
9.0 Mar 04

The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. Ra

CVE-2024-49757 MEDIUM POC
4.9 Oct 25

The open-source identity infrastructure software Zitadel allows administrators to disable the user self-registration. Ra

CVE-2026-109371 HIGH
8.8 Oct 12

Unauthenticated username-change in ZITADEL's hosted Login V1 UI lets a remote attacker rename any active human account -

CVE-2026-105213 HIGH
8.8 Oct 04

ZITADEL 4.x before 4.17.1 fails to check an organization's inactive state during Login V2 authentication, allowing users

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy