---
id: "CVE-2026-119129"
kind: "vulnerability"
aliases: ["CVE-2026-119129"]
title: "ZITADEL: missing authorization in Login V2 lets attackers take victims' OAuth tokens"
severity: "high"
cvss: 8.6
epss: null
exploited: false
status: "open"
category: "infrastructure"
products: []
ecosystems: []
tags: ["identity", "infrastructure", "oauth", "oidc", "self-hosted", "zitadel"]
not_affected_if: ["version-outside-affected-ranges"]
published_at: "2026-10-29T16:18:05+00:00"
first_seen_at: "2026-10-29T16:25:58+00:00"
updated_at: "2026-10-29T16:29:26+00:00"
sources: [{"source": "nvd", "url": "https://nvd.nist.gov/vuln/detail/CVE-2026-119129", "first_seen_at": "2026-10-29T16:25:58+00:00"}]
---

# ZITADEL: missing authorization in Login V2 lets attackers take victims' OAuth tokens

ZITADEL's Login V2 approves OAuth 2.0 device authorizations using a victim's existing session without asking for consent. An attacker who sends a signed-in user a link with the attacker's user code can obtain that user's tokens, and can bypass project access settings through the OIDC device authorization API.

_Summary, check and fix written by a model from the sources; labelled as such._

## How to check

- Check the ZITADEL version running in production: versions 3.0.0 through 3.4.15 and 4.0.0 before 4.19.5 are affected.
- Confirm whether the OAuth 2.0 device authorization flow is enabled for your instance (unknown from sources how to check this).

## Fix

- ZITADEL 4.x: move to a release at or after `4.19.5`.
- ZITADEL 3.x: the sources give no fixed 3.x version; upgrade path unknown.

## Timeline

- 2026-10-29T16:25:58+00:00 nvd https://nvd.nist.gov/vuln/detail/CVE-2026-119129

## From the sources

ZITADEL 3.0.0 through 3.4.15 and 4.0.0 before 4.19.5 contains a missing authorization vulnerability in Login V2 that allows attackers to approve OAuth 2.0 device authorizations using a victim's existing session without consent. Attackers can send a signed-in user a link carrying the attacker's user code to obtain the victim's tokens, and can bypass project access settings via the OIDC device authorization API.

---

_Free to read at a human pace. An API with keys and an MCP server are in preparation; early access: hello@infrastack.ai_