CVE-2026-62429

MEDIUMPre-NVD 6.56.5—
EchelonGraph scoreHIGH confidence

Score 6.5 from GitHub Security Advisory published 2026-07-28. CISA-ADP (Vulnrichment) CVSS v3.1 baseline 6.5; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
Trending — 4 sources updated this week
6.5EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 6.5Exploit: None knownExposed: 0

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

Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest.

CVSS v3
6.5
EG Score
6.5(high)
EG Risk
29(Track)
EG Risk 29/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
Severity65% × 45%
Exploitation0% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
—
EPSS %ILE
—
KEV
Not listed

Published

July 28, 2026

Last Modified

July 28, 2026

Advisory Details (2)

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

XSA-502 - Xen Security Advisories

http://xenbits.xen.org/xsa/advisory-502.html
generic

XSA-502 - Xen Security Advisories

https://xenbits.xenproject.org/xsa/advisory-502.html

Vendor Advisories for CVE-2026-62429(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 / 17× 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-29 17:43 UTCEG score recompute
  2. 2026-07-29 17:43 UTCGHSA enrichment
  3. 2026-07-28 17:24 UTCGHSA enrichment
  4. 2026-07-28 16:56 UTCGHSA enrichment
  5. 2026-07-28 16:21 UTCGHSA enrichment
  6. 2026-07-28 16:19 UTCNVD updateCVSS v3 → 6.5 · severity → MEDIUM
  7. 2026-07-28 16:19 UTCNVD update
  8. 2026-07-28 16:18 UTCEG score recompute▲ 3.20
  9. 2026-07-28 16:18 UTCGHSA enrichment
  10. 2026-07-28 16:13 UTCMITRE cvelistV5CVSS v3 → 6.5 · severity → MEDIUM
  11. 2026-07-28 15:30 UTCEG score recompute▲ 3.30
  12. 2026-07-28 15:29 UTCMITRE cvelistV5CVSS v3 → 3.3 · severity → LOW
  13. 2026-07-28 14:34 UTCNVD update
  14. 2026-07-28 13:43 UTCMITRE cvelistV5
  15. 2026-07-28 13:31 UTCNVD update
  16. 2026-07-28 13:05 UTCEG score recompute
  17. 2026-07-28 13:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-62429?
CVE-2026-62429 is a medium vulnerability published on July 28, 2026. Accessing the vNUMA configuration data of a guest is still possible when domain destruction has already started. The cleaning up of that configuration information is not synchronized with its retrieval by a device model controlling the guest.
When was CVE-2026-62429 disclosed?
CVE-2026-62429 was first published in the National Vulnerability Database on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-62429?
CVE-2026-62429 has a CVSS v3.1 base score of 6.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-62429?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62429, 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-62429

Explore →

Is Your Infrastructure Affected by CVE-2026-62429?

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

Start Free Scan →Browse All CVEs