CVE-2026-56666

MEDIUMPre-NVD 4.84.8—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.8 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 91% 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
Trending — 3 sources updated this week
4.8
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.8Exploit: NoneExposed: 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 4.15.3, ZITADEL's external identity provider handler checks that the local user's email is verified but does not verify that the external IdP confirmed ownership of the same email before auto-linking by email, allowing a permissive provider account with a victim email address to be linked to the victim's local account. This issue is fixed in version 4.15.3.

CVSS v3
4.8
EG Score
4.8(medium)
EPSS
8.7%
KEV
Not listed

Published

July 10, 2026

Last Modified

July 13, 2026

Advisory Details (3)

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

Auto-linking by email: IdP-side email verification is not checked · Advisory · zitadel/zitadel · GitHub

https://github.com/zitadel/zitadel/security/advisories/GHSA-992q-9gwp-7r79
github_release Patch Available

v4.15.3

Patch available: zitadel/zitadel v4.15.3

https://github.com/zitadel/zitadel/releases/tag/v4.15.3
github_commit

commit c97012f0c5dc (zitadel/zitadel)

Fix landed in zitadel/zitadel commit c97012f0c5dc — awaiting tagged release

https://github.com/zitadel/zitadel/commit/c97012f0c5dc2fe960ae6e940cbea23229f0557f

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 14× in last 7d / 14× 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-15 16:57 UTCEPSS rescore
  2. 2026-07-15 16:57 UTCEPSS rescore
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-14 20:25 UTCEG score recompute
  6. 2026-07-13 22:31 UTCEPSS rescore
  7. 2026-07-13 19:47 UTCEG score recompute
  8. 2026-07-13 06:13 UTCEPSS rescore
  9. 2026-07-13 06:13 UTCEPSS rescore
  10. 2026-07-12 19:09 UTCEG score recompute
  11. 2026-07-12 05:46 UTCEPSS rescore
  12. 2026-07-11 18:31 UTCEG score recompute
  13. 2026-07-10 17:53 UTCEG score recompute
  14. 2026-07-10 17:52 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-56666?
CVE-2026-56666 is a medium vulnerability published on July 10, 2026. ZITADEL is an open source identity management platform. Prior to 4.15.3, ZITADEL's external identity provider handler checks that the local user's email is verified but does not verify that the external IdP confirmed ownership of the same email before auto-linking by email, allowing a permissive…
When was CVE-2026-56666 disclosed?
CVE-2026-56666 was first published in the National Vulnerability Database on July 10, 2026, with the most recent update on July 13, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-56666 actively exploited?
CVE-2026-56666 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 8.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-56666?
CVE-2026-56666 has a CVSS v3 base score of 4.8 (NVD).
How do I remediate CVE-2026-56666?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-56666, 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

Explore the affected products and dependency analysis for CVE-2026-56666

Explore →

Is Your Infrastructure Affected by CVE-2026-56666?

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

Start Free Scan →Browse All CVEs