CVE-2026-55672 json
ZITADEL: Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation)
published 4mo ago modified 3mo ago also EUVD-2026-42979 , GHSA-xqxv-4jc2-x56x , GO-2026-5768
- cvss
- 7.4
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/zitadel/zitadel 1.80.0-v2.20.0.20260616131956-0973b074b488
- zitadel zitadel 3.4.12, 4.15.2
- govulncheck-vulndb openSUSE Leap 16.0 0.0.20260723T184607-160000.1.1
opensuse advisories openSUSE-SU-2026:21483-1
Is CVE-2026-55672 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- none
- Automatable
- no
- Technical impact
- total
- Assessed
- 4mo ago
Exploit prediction
0.43% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-11).
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
| GitHub | 3.1 | 7.4 | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/zitadel/zitadel | <1.80.0-v2.20.0.20260616131956-0973b074b488 |
1.80.0-v2.20.0.20260616131956-0973b074b488 |
Affected products
- zitadel zitadel
Classification
References
-
github.com
/zitadel/zitadel/commit/562403079a98cf2059cdac11865a45e2f285be71
web
-
github.com
/zitadel/zitadel/commit/5b1708e0e650398f0ebc3341714f0798b0118917
web
-
github.com
/zitadel/zitadel/commit/0973b074b48816757c47fe732b06d2488d3d284c
web, patch
-
github.com
/zitadel/zitadel/security/advisories/GHSA-xqxv-4jc2-x56x
web, advisory
-
github.com
/zitadel/zitadel/releases/tag/v3.4.12
web
-
github.com
/zitadel/zitadel/releases/tag/v4.15.2
web
-
nvd.nist.gov
/vuln/detail/CVE-2026-55672
advisory
-
github.com
/zitadel/zitadel
package
Sources
- CVE List CVE-2026-55672
- GitHub Advisory GHSA-xqxv-4jc2-x56x
- NVD CVE-2026-55672
- OSV GO-2026-5768
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.