CVE-2026-105208 zitadel CVE debrief

Who should care

Defenders responsible for ZITADEL deployments, particularly those using IdP intent tokens, should assess exposure and prioritize verification and remediation. This includes operators, platform administrators, vulnerability management teams, and security teams who need to review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance.

Why it matters

CVE-2026-105208 allows authenticated users to tamper with IdP intent tokens, potentially leading to session hijacking and lateral movement within ZITADEL deployments. Defenders should prioritize verification and remediation.

• Session hijacking via forgeable IdP intent tokens
• Potential for lateral movement within ZITADEL deployments
• Need for verification of ZITADEL version and IdP intent token implementation
• Possible impact on user authentication and authorization

Technical summary

ZITADEL 4.x before 4.17.3 and 3.x through 3.4.15 protects IdP intent tokens with unauthenticated, malleable encryption, allowing authenticated users to tamper with their own token so it is accepted for another user's external login intent. This vulnerability can lead to session hijacking and lateral movement within ZITADEL deployments. Defenders should prioritize verifying and upgrading to ZITADEL version 4.17.3 or later, and reviewing their IdP intent token implementation for potential vulnerabilities without making unsupported root-cause or exploit claims.

Defensive priority

Defenders should prioritize verifying and upgrading to ZITADEL version 4.17.3 or later, and reviewing their IdP intent token implementation for potential vulnerabilities.

Recommended defensive actions

• Verify and upgrade to ZITADEL version 4.17.3 or later
• Review IdP intent token implementation for potential vulnerabilities
• Monitor for suspicious activity related to IdP intent tokens
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up
• Review compensating controls for exposed systems while remediation is scheduled and verified
• Check relevant monitoring, detection, and logs for exposed assets that need extra review
• Track exceptions, retest remediated assets, and close the item only after evidence is documented

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, but the corpus lacks specific information on affected versions and exploitation. Further verification is required to assess exposure and prioritize remediation. Defenders should review the supplied official advisory or CVE record to validate affected scope, severity, and vendor guidance. The official CVE Program record and NIST NVD detail page offer source-provided CVE metadata and source-specific vulnerability assessment.

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.