CVE-2026-55672

HIGHPre-NVD 7.47.4—
EchelonGraph scoreMEDIUM confidence

This high-severity CVE scores 7.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 80% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
7.4EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 7.4Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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 v3
7.4
EG Score
7.4(medium)
EG Risk
33(Track)
EG Risk 33/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity74% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
20%
KEV
Not listed

Published

June 18, 2026

Last Modified

July 10, 2026

Advisory Details (5)

Auto-updated Jul 10, 2026
Patch available. Sources: github_commit, github_release, github.
github Patch Available

Missing client_id binding in OIDC authorization code exchange and refresh token flows (RFC 6749 Section 4.1.3 violation) · Advisory · zitadel/zitadel · GitHub

https://github.com/zitadel/zitadel/security/advisories/GHSA-xqxv-4jc2-x56x
github_release Patch Available

v4.15.2

Patch available: zitadel/zitadel v4.15.2

https://github.com/zitadel/zitadel/releases/tag/v4.15.2
github_release Patch Available

v3.4.12

Patch available: zitadel/zitadel v3.4.12

https://github.com/zitadel/zitadel/releases/tag/v3.4.12
github_commit

commit 5b1708e0e650 (zitadel/zitadel)

Fix landed in zitadel/zitadel commit 5b1708e0e650 — awaiting tagged release

https://github.com/zitadel/zitadel/commit/5b1708e0e650398f0ebc3341714f0798b0118917
github_commit

commit 562403079a98 (zitadel/zitadel)

Fix landed in zitadel/zitadel commit 562403079a98 — awaiting tagged release

https://github.com/zitadel/zitadel/commit/562403079a98cf2059cdac11865a45e2f285be71

Vendor Advisories for CVE-2026-55672(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
Go(1)
PackageVulnerable rangeFixed inDependents
github.com/zitadel/zitadel—1.80.0-v2.20.0.20260616131956-0973b074b488—

Weakness Classification(2)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 11× in last 7d / 29× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-30 22:33 UTCEG score recompute
  2. 2026-07-30 16:28 UTCEPSS rescore
  3. 2026-07-30 03:12 UTCEG score recompute
  4. 2026-07-30 01:30 UTCEPSS rescore
  5. 2026-07-29 01:48 UTCEG score recompute
  6. 2026-07-28 15:37 UTCEPSS rescore
  7. 2026-07-27 22:15 UTCEG score recompute
  8. 2026-07-26 18:46 UTCEG score recompute
  9. 2026-07-26 14:54 UTCEPSS rescore
  10. 2026-07-25 14:18 UTCEPSS rescore
  11. 2026-07-24 14:18 UTCEPSS rescore
  12. 2026-07-23 14:18 UTCEPSS rescore
  13. 2026-07-23 03:20 UTCEG score recompute
  14. 2026-07-22 14:08 UTCEPSS rescore
  15. 2026-07-21 15:25 UTCEPSS rescore
  16. 2026-07-20 17:08 UTCEPSS rescore
  17. 2026-07-19 14:31 UTCEPSS rescore
  18. 2026-07-19 14:31 UTCEPSS rescore
  19. 2026-07-19 02:29 UTCEPSS rescore
  20. 2026-07-18 10:04 UTCEPSS rescore
  21. 2026-07-16 17:03 UTCEPSS rescore
  22. 2026-07-15 16:57 UTCEPSS rescore
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 02:00 UTCEPSS rescore
  25. 2026-07-15 02:00 UTCEPSS rescore
Show 5 more
  1. 2026-07-13 22:31 UTCEPSS rescore
  2. 2026-07-13 06:13 UTCEPSS rescore
  3. 2026-07-13 06:13 UTCEPSS rescore
  4. 2026-07-12 05:46 UTCEPSS rescore
  5. 2026-06-18 14:06 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55672?
CVE-2026-55672 is a high vulnerability published on June 18, 2026. 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…
When was CVE-2026-55672 disclosed?
CVE-2026-55672 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on July 10, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-55672 actively exploited?
CVE-2026-55672 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 80.2% of all scored CVEs.
What is the CVSS score of CVE-2026-55672?
CVE-2026-55672 has a CVSS v3 base score of 7.4 (NVD).
How do I remediate CVE-2026-55672?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55672, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-55672

Explore →

Is Your Infrastructure Affected by CVE-2026-55672?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs