CVE-2026-55670

LOWPre-NVD 2.32.3—
EchelonGraph scoreMEDIUM confidence

This low-severity CVE scores 2.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.3%, top 79% 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
2.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 2.3Exploit: 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.1, ZITADEL's event store validation can retain the original resource owner for a deleted user identifier, causing a later user recreated with the same identifier in another organization to be provisioned under the original organization and exposed to that organization's administrator. This issue is fixed in version 4.15.2.

CVSS v3
2.3
EG Score
2.3(medium)
EG Risk
10(Track)
EG Risk 10/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
Severity23% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
20.7%
KEV
Not listed

Published

June 18, 2026

Last Modified

July 10, 2026

References (4)

Vendor Advisories for CVE-2026-55670(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.20260615092437-6082e59d47c1—

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 10× in last 7d / 21× 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-24 14:18 UTCEPSS rescore
  2. 2026-07-23 14:18 UTCEPSS rescore
  3. 2026-07-23 03:20 UTCEG score recompute
  4. 2026-07-22 14:08 UTCEPSS rescore
  5. 2026-07-21 15:25 UTCEPSS rescore
  6. 2026-07-20 17:08 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 14:31 UTCEPSS rescore
  9. 2026-07-19 02:29 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-16 17:03 UTCEPSS rescore
  12. 2026-07-15 16:57 UTCEPSS rescore
  13. 2026-07-15 16:57 UTCEPSS rescore
  14. 2026-07-15 02:00 UTCEPSS rescore
  15. 2026-07-15 02:00 UTCEPSS rescore
  16. 2026-07-13 22:31 UTCEPSS rescore
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-12 05:46 UTCEPSS rescore
  20. 2026-07-10 17:53 UTCEG score recompute▲ 2.30
  21. 2026-07-10 17:52 UTCMITRE cvelistV5CVSS v3 → 2.3 · CVSS v4 → 2.3
  22. 2026-06-18 13:45 UTCEG score recompute

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-55670?
CVE-2026-55670 is a low vulnerability published on June 18, 2026. ZITADEL is an open source identity management platform. Prior to 4.15.1, ZITADEL's event store validation can retain the original resource owner for a deleted user identifier, causing a later user recreated with the same identifier in another organization to be provisioned under the original…
When was CVE-2026-55670 disclosed?
CVE-2026-55670 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-55670 actively exploited?
CVE-2026-55670 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 20.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-55670?
CVE-2026-55670 has a CVSS v3 base score of 2.3 (NVD).
How do I remediate CVE-2026-55670?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-55670, 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-55670

Explore →

Is Your Infrastructure Affected by CVE-2026-55670?

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

Start Free Scan →Browse All CVEs