High 7.4Published Jul 10, 2026

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

Updated under an hour ago (Oct 26, 2026, 1:00 PM ET)

Does this affect you?

It affects zitadel. Add what you run to find out whether that includes you.

No exploitation reported and no EPSS estimate yet.

Do this next

Start free and add your stack

Free account, 1 product

Every CVE for zitadel

Exploited in the last 30 days

ZITADEL is an open source identity management platform. Prior to 3.4.12 and 4.15.2, ZITADEL's OAuth2 and OIDC CodeExchange, RefreshToken, and device token flows fail to verify that the requesting client matches the client that initiated the authorization flow, allowing intercepted grants or refresh tokens to be exchanged under a different client. This issue is fixed in versions 3.4.12 and 4.15.2.

CVSS: 7.4 HIGH (v3.1, CNA)CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Weakness (CWE): CWE-287, CWE-863
Known exploited: Not in CISA's KEV catalog
EPSS (exploitation in the next 30 days): Not loaded for this CVE
Assigned by: GitHub_M
NVD analysis: Deferred
Record last updated: Jul 10, 2026
First seen by InfoSec Signals: Oct 9, 2026

Affected products

Affected products

zitadel zitadel zitadel:zitadel (from the name)	from 4.0.0-rc.1, < 4.15.2; before 3.4.12	CNA record

References

References

https://github.com/zitadel/zitadel/security/advisories/GHSA-xqxv-4jc2-x56x	x-refsource-confirm
https://github.com/zitadel/zitadel/commit/562403079a98cf2059cdac11865a45e2f285be71	x-refsource-misc
https://github.com/zitadel/zitadel/commit/5b1708e0e650398f0ebc3341714f0798b0118917	x-refsource-misc
https://github.com/zitadel/zitadel/releases/tag/v3.4.12	x-refsource-misc
https://github.com/zitadel/zitadel/releases/tag/v4.15.2	x-refsource-misc

The CVE record on cve.org NVD's entry

The CVE record is authoritative. Products marked “from the name” were identified from the CNA's free-text names, not a CPE, and are matched less certainly. This product uses the NVD API but is not endorsed or certified by the NVD.