CVE-2026-62430

HIGHPre-NVD 7.57.5—
EchelonGraph scoreHIGH confidence

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

Triggered by: GitHub Security Advisory CVSS
Sources: cisa-adp, ghsa
Trending — 4 sources updated this week
7.5EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: —CVSS: 7.5Exploit: None knownExposed: 0

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

Accesses to the CMOS memory contents are done using an indirect IO port pair. Therefore Xen needs to cache the guest chosen index, and one of the usages of the index didn't take the necessary locking to avoid concurrent changes. As a result, a guest could change the index after it being checked, causing a subsequent out-of-bound read access to the contents of an array.

CVSS v3
7.5
EG Score
7.5(high)
EG Risk
49(Track)
EG Risk 49/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
Severity75% × 45%
Exploitation0% × 40%
Automatability100% × 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-503 - Xen Security Advisories

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

XSA-503 - Xen Security Advisories

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

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

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2026-62430?
CVE-2026-62430 is a high vulnerability published on July 28, 2026. Accesses to the CMOS memory contents are done using an indirect IO port pair. Therefore Xen needs to cache the guest chosen index, and one of the usages of the index didn't take the necessary locking to avoid concurrent changes. As a result, a guest could change the index after it being checked,…
When was CVE-2026-62430 disclosed?
CVE-2026-62430 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-62430?
CVE-2026-62430 has a CVSS v3.1 base score of 7.5 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-62430?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62430, 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-62430

Explore →

Is Your Infrastructure Affected by CVE-2026-62430?

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

Start Free Scan →Browse All CVEs