Is CVE-2026-119129 exploited in the wild?

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

How severe is CVE-2026-119129?

High severity, with a CVSS score of 8.1, published 29 October 2026.

Which products and versions are affected?

ZITADEL 3.0.0 through 3.4.15, 4.0.0 before 4.19.5.

How is CVE-2026-119129 attacked?

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

Am I affected by CVE-2026-119129?

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-119129: ZITADEL missing authorization in Login V2 device authorization

CVE-2026-119129 · Severity: high · CVSS 8.1 · Published 2026-10-29

ZITADEL is an identity and access management platform that handles user authentication and OAuth token issuance. A missing authorization flaw in its Login V2 interface allows attackers to trick signed-in users into approving OAuth device authorizations by simply clicking a link, granting the attacker the victim's authentication tokens and potential administrative access. This enables one-click account takeover and bypasses access controls on protected applications.

Technologies: ZITADEL. Vendors: ZITADEL.

Quick answers

Is CVE-2026-119129 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-119129 being exploited in the wild.
How severe is CVE-2026-119129?: High severity, with a CVSS score of 8.1, published 29 October 2026.
Which products and versions are affected?: ZITADEL 3.0.0 through 3.4.15, 4.0.0 before 4.19.5.
Is there a fix for CVE-2026-119129?: Yes: fixed in 4.19.5 and later; 3.x line reached end-of-life and will not receive a patch. Until then: If the Device Authorization (Device Code) flow is not required, remove the Device Code grant type from all applications to prevent exploitation of both the UI and API vectors. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-119129 attacked?: It is attacked over the network, in a hosted service.
Am I affected by CVE-2026-119129?: 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: 4.19.5 and later; 3.x line reached end-of-life and will not receive a patch

If the Device Authorization (Device Code) flow is not required, remove the Device Code grant type from all applications to prevent exploitation of both the UI and API vectors.

Technical details

The vulnerability is a missing authorization check (CWE-862) in the Device Authorization flow. When a user with an active Login V2 session visits the device authorization approval page, the application automatically approves any pending authorization without requiring the user to enter the device code or provide explicit consent. The same flaw exists in the OIDC service API endpoint that custom login UIs use, which additionally fails to enforce project access control restrictions.

Affected products

ZITADEL ZITADEL 3.0.0 through 3.4.15, 4.0.0 before 4.19.5

Timeline

2026-10-29: advisory: GitHub Security Advisory published

References

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