CVE-2026-62427

HIGHPre-NVD 8.88.8—
EchelonGraph scoreHIGH confidence

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

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

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

[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.]

To manage the system, sysctl and platform operations are used by the control domain or a possible Xenstore domain. Some of these operations may not be executed in parallel, so a system-wide lock each is used. The way those locks are acquired is, however, not providing any fairness. Furthermore, with XSM/Flask in use, the lock acquire will, for some operations, occur ahead of any permission checking.

The sysctl issue is CVE-2026-62426.

The platform-op issue is CVE-2026-62427.

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

Published

July 28, 2026

Last Modified

July 28, 2026

Advisory Details (1)

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

XSA-499 - Xen Security Advisories

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

Vendor Advisories for CVE-2026-62427(1)

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

Weakness Classification(2)

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

Data Freshness Timeline

(refreshed 22× in last 7d / 22× 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-31 10:25 UTCGHSA enrichment
  2. 2026-07-30 21:12 UTCEG score recompute
  3. 2026-07-30 21:12 UTCGHSA enrichment
  4. 2026-07-30 16:28 UTCEPSS rescore
  5. 2026-07-30 08:02 UTCEG score recompute
  6. 2026-07-30 08:01 UTCGHSA enrichment
  7. 2026-07-30 01:30 UTCEPSS rescore
  8. 2026-07-30 01:30 UTCEPSS rescore
  9. 2026-07-29 18:49 UTCGHSA enrichment
  10. 2026-07-29 05:36 UTCEG score recompute
  11. 2026-07-29 05:36 UTCGHSA enrichment
  12. 2026-07-28 16:21 UTCGHSA enrichment
  13. 2026-07-28 16:19 UTCNVD updateCVSS v3 → 8.8 · severity → HIGH
  14. 2026-07-28 16:19 UTCNVD update
  15. 2026-07-28 16:18 UTCEG score recompute▲ 3.30
  16. 2026-07-28 16:18 UTCGHSA enrichment
  17. 2026-07-28 16:13 UTCMITRE cvelistV5CVSS v3 → 8.8 · severity → HIGH
  18. 2026-07-28 15:30 UTCEG score recompute▲ 5.50
  19. 2026-07-28 15:29 UTCMITRE cvelistV5CVSS v3 → 5.5 · severity → MEDIUM
  20. 2026-07-28 13:31 UTCNVD update
  21. 2026-07-28 13:05 UTCEG score recompute
  22. 2026-07-28 13:03 UTCMITRE cvelistV5first tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-62427?
CVE-2026-62427 is a high vulnerability published on July 28, 2026. [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] To manage the system, sysctl and platform operations are used by the control domain or a possible Xenstore domain. Some of these operations may not be executed in…
When was CVE-2026-62427 disclosed?
CVE-2026-62427 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.
Is CVE-2026-62427 actively exploited?
CVE-2026-62427 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0% probability of exploitation in the next 30 days, which ranks it in the top 83.6% of all scored CVEs.
What is the CVSS score of CVE-2026-62427?
CVE-2026-62427 has a CVSS v3.1 base score of 8.8 (CISA-ADP / Vulnrichment enrichment; NVD's own analysis pending).
How do I remediate CVE-2026-62427?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-62427, 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-62427

Explore →

Is Your Infrastructure Affected by CVE-2026-62427?

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

Start Free Scan →Browse All CVEs