CVE-2026-105207: ZITADEL Cloud-Native IAM Unauthenticated Account Takeover via External IdP Linking
HERMES THREAT SCORE & IDENTITY PERIMETER COMPROMISE EVALUATION
Target:ZITADEL Cloud-Native IAM โ User Service V2 & Login V2 (AddIDPLink) Both CVSS v3.1 (9.8 Critical) and the Hermes Threat Score (96 CRITICAL) classify CVE-2026-105207 as a catastrophic identity gateway compromise. ZITADEL operates as an enterprise-grade cloud-native identity and access management (IAM) perimeter platform, orchestrating OAuth2/OIDC single sign-on, SAML assertions, and Passkey enrollments across multi-tenant organizations. The failure to verify caller authentication or existing primary factors during external Identity Provider (IdP) linking permits unauthenticated remote adversaries knowing a target username or email to silently link attacker-controlled Google or GitHub accounts to enterprise administrators. Once linked, logging in via the external IdP mints valid organization administrator tokens, granting complete control over tenant IAM configurations, user directories, and downstream integrated services.
CVE-2026-105207: ZITADEL Cloud-Native IAM Unauthenticated Account Takeover via External IdP LinkingVULNERABILITY
Software platform affected by security vulnerabilities and agentic attack patterns.
๐ Why is this related? (Evidence & Provenance)
“Confirmed security vulnerability in ZITADEL Identity & Access Management documented in Hermes dossier.”
- [vulnerability_report]
- [government_confirmation]CISA verified active exploitation in the wild and mandated federal remediation deadline in KEV entry. — Source: Cybersecurity & Infrastructure Security Agency (CISA): CISA Adds CVE-2026-59822 to Known Exploited Vulnerabilities Catalog (Reliability: VERY_HIGH)
1. Technical Context & Affected Software Matrix
Section titled โ1. Technical Context & Affected Software MatrixโZITADEL is deployed as a sovereign identity broker and authorization gateway across Kubernetes clusters and cloud environments, federating identity across enterprise microservices.
| Parameter | Technical Specification | Operational Details |
|---|---|---|
| CVE Identifier | CVE-2026-105207 | International security tracking identifier |
| Software Platform | ZITADEL Cloud-Native IAM | Open-source Go-based IAM & OAuth2/OIDC identity provider |
| Vulnerable Component | internal/user/repository/view / AddIDPLink | User Service V2 & Login V2 IdP linking handler |
| Vulnerability Class | CWE-287 / CWE-306 / CWE-862 | Improper Authentication / Missing Factor Verification |
| Attack Vector | Network (Port 80/443 TCP) | Remote, unauthenticated gRPC or HTTP POST request |
| Remediation Release | ZITADEL v4.17.3 | Enforces verified primary factor check before IdP association |
[ Unauthenticated Remote Attacker ] | Knows victim username: admin@target-corp.com Owns external IdP identity: attacker@gmail.com | v +------------------------------------------+ | ZITADEL Identity Gateway (:443 TCP) | | Login V2 / User Service V2 gRPC API | +------------------------------------------+ | [ AddIDPLink / Identify-Only Session ] NO check for existing primary factor! NO check for caller authorization! | v +------------------------------------------+ | ZITADEL User Repository / Event Store | | Binds attacker@gmail.com to target | | admin@target-corp.com account record | +------------------------------------------+ | v +------------------------------------------+ | Attacker Logs in via Google SSO | | ZITADEL maps attacker identity to | | victim administrator account profile | +------------------------------------------+ | v +------------------------------------------+ | Full Tenant Administrator Takeover | | Mints high-privilege JWTs / Org Owner | +------------------------------------------+2. Root Cause Analysis & Vulnerable Code Anatomy
Section titled โ2. Root Cause Analysis & Vulnerable Code AnatomyโThe root cause of CVE-2026-105207 is a missing state validation check within the IdP linking workflow. In ZITADELโs event-sourced architecture, user commands emit state events to the eventstore.
When linking an external IdP, the handler AddIDPLink processed incoming requests without confirming that the current session context held a verified primary authentication factor (PrimaryFactorVerified == true):
// Vulnerable logic in ZITADEL User Service V2 (ZITADEL < 4.17.3)func (s *Server) AddIDPLink(ctx context.Context, req *user.AddIDPLinkRequest) (*user.AddIDPLinkResponse, error) { // FLAW: Checked only if user exists, not if caller is authenticated or authorized! targetUser, err := s.command.GetUserByID(ctx, req.UserId) if err != nil { return nil, status.Errorf(codes.NotFound, "user not found") }
// In Login V2 identify sessions, the session state only requires 'identified' // without requiring completed password or passkey verification! idpLink := &domain.UserIDPLink{ IDPConfigID: req.IdpConfigId, ExternalUserID: req.ExternalUserId, DisplayName: req.DisplayName, }
// Directly appends the link event to the eventstore err = s.command.AddUserIDPLink(ctx, targetUser.ResourceOwner, targetUser.ID, idpLink) if err != nil { return nil, status.Errorf(codes.Internal, "failed to add idp link: %v", err) }
return &user.AddIDPLinkResponse{}, nil}In Login V2, when a user entered their login name, the session transitioned to the Identified state. If the tenant allowed external identity linking, the frontend presented the option to bind an external IdP. Because the backend failed to verify that the user had already solved a primary credential challenge (password, Passkey, or WebAuthn factor), an unauthenticated attacker could initiate this flow, authenticate to their own external IdP (e.g. Google), and complete the callback, binding their identity to the victimโs account.
In ZITADEL v4.17.3, the engineering team patched both the gRPC handler and the Login V2 state machine by introducing mandatory permission checks and factor validation:
// Patched logic in ZITADEL v4.17.3func (s *Server) AddIDPLink(ctx context.Context, req *user.AddIDPLinkRequest) (*user.AddIDPLinkResponse, error) { // 1. Verify caller has explicit write permissions or is operating on self with verified session if err := s.checkPermission(ctx, domain.PermissionUserWrite, req.UserId); err != nil { // If modifying self, ensure primary factor has been successfully verified in current session session, sessionErr := s.getActiveSession(ctx) if sessionErr != nil || !session.PrimaryFactorVerified() { return nil, status.Errorf(codes.PermissionDenied, "primary factor verification required before linking IdP") } }
// 2. Proceed with validated IdP linking event return s.command.AddUserIDPLinkVerified(ctx, req)}3. Attack Execution Flow & Weaponization Mechanics
Section titled โ3. Attack Execution Flow & Weaponization MechanicsโsequenceDiagram autonumber actor Attacker as Unauthenticated Attacker participant ZITADEL as ZITADEL Gateway (:443) participant ExtIdP as Attacker External IdP (Google) participant EventStore as ZITADEL EventStore / DB participant TargetApp as Integrated Corporate App
Attacker->>ZITADEL: POST /v2/sessions/create (loginName: "admin@corp.com") Note over ZITADEL: Session enters "Identified" state (no password checked) Attacker->>ZITADEL: POST /v2/users/admin_id/idp_links (IdP: Google, AttackerSub: "1098234") Note over ZITADEL: Missing auth check: links AttackerSub to admin@corp.com ZITADEL->>EventStore: Commit UserIDPLinkAddedEvent Attacker->>ZITADEL: GET /oauth/v2/authorize (Client: CorporatePortal) ZITADEL->>ExtIdP: Redirect to Google OAuth Attacker->>ExtIdP: Authenticate with Attacker Google Account (1098234) ExtIdP->>ZITADEL: OAuth Callback (sub: "1098234") Note over ZITADEL: Matches linked profile: resolves to admin@corp.com ZITADEL->>Attacker: Issue Admin Session Cookie & Access Token (roles: ["ORG_OWNER"]) Attacker->>TargetApp: Access Corporate Portal with Org Administrator privilegesWeaponization Attributes
Section titled โWeaponization Attributesโ- Zero-factor bypass: Attackers do not need to crack, brute-force, or phish the victimโs password. Multi-factor authentication (MFA/TOTP/Passkeys) configured on the local account is bypassed because external IdP federation delegates the primary factor to the attackerโs IdP.
- Persistence: The attacker-controlled external IdP link remains permanently associated with the victimโs account in the ZITADEL eventstore until manually revoked by another administrator.
- Audit masking: The login appears in authentication logs as a valid federated SSO login originating from the configured external IdP.
4. Forensic Investigation & Threat Hunting
Section titled โ4. Forensic Investigation & Threat HuntingโDetecting CVE-2026-105207 exploitation requires inspecting ZITADEL audit events for unexpected external IdP link additions and correlating new links with subsequent administrative logins.
title: ZITADEL Suspicious External IdP Link Additionid: 3c8192a4-11e0-4927-b521-105207e88001status: experimentaldescription: Detects the addition of external Identity Provider links to privileged ZITADEL accounts within short intervals before administrative session creation, characteristic of CVE-2026-105207 exploitation.references: - https://github.com/zitadel/zitadel/security/advisories/GHSA-g8gj-gq47-xgf4 - https://hermes-codex.vercel.app/cve/2026/cve-2026-105207/author: Hermes Codex Cyber Intelligencedate: 2026-10-06logsource: category: application product: zitadeldetection: selection_event: event_type: 'user.human.idp.link.added' selection_caller: caller_authenticated: false condition: selection_event and selection_callerfalsepositives: - Legitimate self-service onboarding flows on newly created accounts (should still verify primary factor)level: criticaltags: - attack.initial_access - attack.persistence - attack.t1078.004-- Query ZITADEL PostgreSQL eventstore for suspicious IdP link events-- Detect accounts that had an IdP link added without prior password/MFA verificationSELECT e.event_sequence, e.created_at, e.aggregate_id AS user_id, e.event_type, e.payload->>'idpConfigId' AS idp_config_id, e.payload->>'externalUserId' AS external_user_id, e.payload->>'displayName' AS idp_display_name, e.editor_userFROM eventstore.events eWHERE e.event_type = 'user.human.idp.link.added' AND e.created_at >= NOW() - INTERVAL '14 days'ORDER BY e.created_at DESC;#!/usr/bin/env bash# Quick forensic triage for ZITADEL containers / hostsecho "[*] Auditing ZITADEL version..."if command -v zitadel &>/dev/null; then zitadel versionelse echo "[-] zitadel binary not in PATH. Check container image tag."fi
echo "[*] Checking container logs for User Service V2 AddIDPLink calls..."docker logs $(docker ps -q -f name=zitadel) 2>&1 | grep -i -E "AddIDPLink|idp.link.added" | tail -n 30 || true
echo "[*] Verifying reverse proxy gRPC access logs for unauthenticated AddIDPLink calls..."grep -i "AddIDPLink" /var/log/nginx/access.log /var/log/caddy/access.log 2>/dev/null | tail -n 30 || true5. Remediation Strategy & Mitigation
Section titled โ5. Remediation Strategy & Mitigationโ-
Upgrade to ZITADEL v4.17.3 or Later: Upgrade your ZITADEL container image immediately in your Helm values or Docker Compose deployment:
image:repository: ghcr.io/zitadel/zitadeltag: v4.17.3Execute the required database migrations during deployment startup:
Terminal window zitadel setup --config /zitadel-config.yaml -
Audit and Purge Rogue IdP Links: Run an audit query against the user repository to identify any external IdP links established on privileged accounts (
ORG_OWNER,IAM_ADMIN) that do not match enterprise domain emails. Revoke any unrecognized links immediately via the Console UI or Management API (RemoveIDPLink). -
Temporarily Disable Self-Service IdP Linking: If upgrading cannot be completed immediately, navigate to Console > Organization Settings > Login Policy and disable โAllow external Identity Provider linking during loginโ to block unauthenticated linking attempts.