Skip to main content
VulnerabilityPublished Updated

CVE-2026-55672: ZITADEL · Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation)

Affects github.com/zitadel/zitadelSource GCVE Database

0
Compare

Not known to be exploited · CVSS 7.4 High : upgrade to 1.80.0-v2.20.0.20260616131956-0973b074b488 soon.

Data as of 30 Oct 2026, 06:59 UTC

CVSS 3.1 base score
7.4High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.4% chance of exploitation in 30 days – higher than 37% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
Patch
Available – fixed in 1.80.0-v2.20.0.20260616131956-0973b074b488
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 18 Jun 2026

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponized: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 29 Oct 2026.

What to do

Upgrade github.com/zitadel/zitadel to 1.80.0-v2.20.0.20260616131956-0973b074b488.

Affected software

ProductAffectedFixed in
Gogithub.com/zitadel/zitadelAffected
  • <1.80.0-v2.20.0.20260616131956-0973b074b488
Fixed in
  • 1.80.0-v2.20.0.20260616131956-0973b074b488

Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.

AI-suggested

A fix is available. Upgrade Zitadel to version 3.4.12 or later for the 3.x series, or 4.15.2 or later for the 4.x series to restore strict client identity validation on authorization code and refresh token exchanges. Until patched, enforce PKCE for all clients to mitigate authorization code injection risks, minimize refresh token lifespans, and maintain strong application security to prevent token theft. No other workarounds fully address the vulnerability.

Description

Zitadel OAuth2/OIDC implementations in versions 3.0.0 through 3.4.11 and 4.0.0 through 4.15.1 omit client_id binding during authorization code exchange and refresh token flows, violating RFC 6749 Section 4.1.3. This allows an attacker who intercepts authorization codes or refresh tokens to use them with a different client identity, potentially gaining unauthorized access. Exploitation requires prior compromise or token theft in the application environment. PKCE mitigates some risks for authorization code injection but not refresh token misuse. The issue is fixed in versions 3.4.12 and 4.15.2 and later.

References

Community reviews

Loading reviews…