CVE-2026-23556

CRITICALPre-NVD 9.49.4—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.1%, top 96% 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
9.4
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 9.4Exploit: NoneExposed: 0

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

When oxenstored is tearing a domain down, the node data is cleaned up but the usage counts are leaked.

When the domain ID is eventually reused, the new domain can create fewer nodes before beeing deemed to be over quota.

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

Published

July 9, 2026

Last Modified

July 9, 2026

Advisory Details (1)

Auto-updated Jul 9, 2026
No patch confirmed yet.
generic

XSA-483 - Xen Security Advisories

https://xenbits.xen.org/xsa/advisory-483.html

Vendor Advisories for CVE-2026-23556(1)

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

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 17× in last 7d / 68× 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-23 03:07 UTCEG score recompute
  2. 2026-07-22 14:08 UTCEPSS rescore
  3. 2026-07-21 15:24 UTCEPSS rescore
  4. 2026-07-21 15:24 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-19 02:28 UTCEPSS rescore
  10. 2026-07-18 10:04 UTCEPSS rescore
  11. 2026-07-18 10:04 UTCEPSS rescore
  12. 2026-07-17 02:46 UTCGHSA enrichment
  13. 2026-07-16 22:38 UTCGHSA enrichment
  14. 2026-07-16 18:29 UTCGHSA enrichment
  15. 2026-07-16 17:03 UTCEPSS rescore
  16. 2026-07-16 17:03 UTCEPSS rescore
  17. 2026-07-16 14:14 UTCGHSA enrichment
  18. 2026-07-16 10:04 UTCGHSA enrichment
  19. 2026-07-16 05:56 UTCGHSA enrichment
  20. 2026-07-16 01:48 UTCGHSA enrichment
  21. 2026-07-15 21:39 UTCGHSA enrichment
  22. 2026-07-15 17:28 UTCGHSA enrichment
  23. 2026-07-15 16:57 UTCEPSS rescore
  24. 2026-07-15 16:57 UTCEPSS rescore
  25. 2026-07-15 13:09 UTCGHSA enrichment
Show 43 more
  1. 2026-07-15 09:00 UTCGHSA enrichment
  2. 2026-07-15 04:44 UTCGHSA enrichment
  3. 2026-07-15 02:00 UTCEPSS rescore
  4. 2026-07-15 02:00 UTCEPSS rescore
  5. 2026-07-15 00:23 UTCGHSA enrichment
  6. 2026-07-14 20:14 UTCGHSA enrichment
  7. 2026-07-14 16:06 UTCGHSA enrichment
  8. 2026-07-14 11:55 UTCGHSA enrichment
  9. 2026-07-14 07:46 UTCGHSA enrichment
  10. 2026-07-14 03:32 UTCGHSA enrichment
  11. 2026-07-13 23:24 UTCGHSA enrichment
  12. 2026-07-13 22:30 UTCEPSS rescore
  13. 2026-07-13 19:15 UTCGHSA enrichment
  14. 2026-07-13 15:06 UTCGHSA enrichment
  15. 2026-07-13 10:56 UTCGHSA enrichment
  16. 2026-07-13 06:47 UTCGHSA enrichment
  17. 2026-07-13 06:13 UTCEPSS rescore
  18. 2026-07-13 06:13 UTCEPSS rescore
  19. 2026-07-13 02:38 UTCGHSA enrichment
  20. 2026-07-12 22:29 UTCGHSA enrichment
  21. 2026-07-12 18:20 UTCGHSA enrichment
  22. 2026-07-12 14:12 UTCGHSA enrichment
  23. 2026-07-12 10:01 UTCGHSA enrichment
  24. 2026-07-12 05:52 UTCGHSA enrichment
  25. 2026-07-12 05:46 UTCEPSS rescore
  26. 2026-07-12 05:46 UTCEPSS rescore
  27. 2026-07-12 01:43 UTCGHSA enrichment
  28. 2026-07-11 21:33 UTCGHSA enrichment
  29. 2026-07-11 17:25 UTCGHSA enrichment
  30. 2026-07-11 13:16 UTCGHSA enrichment
  31. 2026-07-11 09:07 UTCGHSA enrichment
  32. 2026-07-11 08:27 UTCEPSS rescore
  33. 2026-07-11 04:58 UTCGHSA enrichment
  34. 2026-07-11 00:49 UTCGHSA enrichment
  35. 2026-07-10 20:40 UTCGHSA enrichment
  36. 2026-07-10 16:30 UTCGHSA enrichment
  37. 2026-07-10 12:22 UTCGHSA enrichment
  38. 2026-07-10 08:12 UTCGHSA enrichment
  39. 2026-07-10 04:04 UTCGHSA enrichment
  40. 2026-07-09 23:55 UTCGHSA enrichment
  41. 2026-07-09 19:46 UTCGHSA enrichment
  42. 2026-07-09 15:37 UTCEG score recompute
  43. 2026-07-09 15:35 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-23556?
CVE-2026-23556 is a critical vulnerability published on July 9, 2026. When oxenstored is tearing a domain down, the node data is cleaned up but the usage counts are leaked. When the domain ID is eventually reused, the new domain can create fewer nodes before beeing deemed to be over quota.
When was CVE-2026-23556 disclosed?
CVE-2026-23556 was first published in the National Vulnerability Database on July 9, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-23556 actively exploited?
CVE-2026-23556 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 3.5% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-23556?
CVE-2026-23556 has a CVSS v3 base score of 9.4 (NVD).
How do I remediate CVE-2026-23556?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-23556, 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-23556

Explore →

Is Your Infrastructure Affected by CVE-2026-23556?

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

Start Free Scan →Browse All CVEs