All vulnerabilities

Servers and applications

CVE-2026-55672

Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation)

Severity
High 7.4
Published
17 Jun 2026
Last changed
19 Jun 2026
Added to UpHeron
3 Nov 2026
Fixed in
3.4.12, 4.15.2
Exploit chance
0.4% in the next 30 daysHigher than 38% of CVEs. EPSS by FIRST, 19 Nov 2026
Weakness
Improper authentication (CWE-287)Incorrect authorization (CWE-863)
Attack
Over the network · Only under certain conditions · No login needed · No user action needed
Attacker can
Read data · Change data
CVSS vector
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Also known as
GHSA-xqxv-4jc2-x56x
Sources
Project advisories (GitHub)

Description

Zitadel's OAuth2 / OIDC CodeExchange and RefreshToken implementations omit a critical validation step to ensure that the requesting client matches the client that originally initiated the authorization flow. This violates RFC 6749 Section 4.1.3, which mandates that the authorization server must ensure the authorization code was issued to the authenticated confidential client.

This flaw creates potential vulnerabilities in two main authentication phases, provided specific external preconditions are met:

  • Authorization Code Injection: An attacker who intercepts an authorization code (via an independent application vulnerability such as XSS, referrer leakage, log access, or network interception) can exchange it using credentials from a completely different client (ClientB) registered on the same Zitadel instance. Zitadel will authenticate ClientB and issue tokens for the victim user without verifying the client binding.
From zitadel/zitadel's security advisory. Shortened; the full text is there.

Workarounds

  • External Preconditions: It is critical to note that exploiting either vector requires a pre-existing vulnerability or data leak within the target application environment to intercept the code or token in the first place. Securing the application layer against token theft remains outside the scope of Zitadel.
  • Multi-tenant risk: On shared or multi-tenant instances, a client belonging to one tenant could theoretically exploit codes/tokens belonging to another tenant's clients if they are successfully intercepted.
Workarounds as given by zitadel/zitadel's security advisory.

Affected software

SoftwareAffected versions
ZITADELServers and applications · github:zitadel/zitadel
  • Every version before 3.4.12
  • From 4.0.0 before 4.15.2

About ZITADEL

ZITADEL - Identity infrastructure, simplified for you.

From its GitHub repository.
GitHub stars
15,585GitHub, 15 Nov 2026
Forks
1,432GitHub, 15 Nov 2026
Latest release
v4.20.3GitHub, 15 Nov 2026
Released
13 Nov 2026GitHub
License
AGPL-3.0GitHub
First published on GitHub
16 Mar 2020GitHub

References