CVE-2025-27463

CRITICALPre-NVD 9.49.4
EchelonGraph scoreMEDIUM confidence

“—” beside the score: it is equal to the CVSS score beside it.

This critical-severity CVE scores 9.4 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2% (4th percentile of EPSS-scored CVEs). No GitHub Security Advisory CVSS is on record for this CVE.

Triggered by: Headline CVSS from a secondary CVSS source
Sources: EPSS, a secondary CVSS source
9.4EG
EchelonGraph verdictPlan mitigationRemediate within your standard update timelines (the SSVC decision on this page).
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: 0.2%CVSS: 9.4Exploit: None knownExposed services: Not assessed

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

[This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The Windows PV drivers expose various facilities to userspace. Several of these have no security descriptor, and are therefore fully accessible to unprivileged users. These are: 1. XenCons, CVE-2025-27462 2. XenIface, CVE-2025-27463 3. XenBus, CVE-2025-27464

CVSS v3
9.4
EG Score
9.4CRITICALmedium confidence
EG Risk
42
EG Risk 42/100

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 (value × EchelonGraph’s weight)
Severity94% × 45%
The EG Score, 9.4 of 10.
Exploitation0.2% × 40%
FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low or medium mission impact; Track* at high (mission-essential systems).
Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.
EPSS PROB
0.2%
EPSS %ILE
4th
KEV
Not listed

SSVC (CISA's decision table, applied by EchelonGraph)Track at low or medium mission impact; Track* at high (mission-essential systems).

No fix is confirmed yet. Restrict network exposure of the affected system or apply the vendor's mitigation within your standard update timelines, and watch the vendor's advisory for the fix.

Exploitation none (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.

In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

Published

July 9, 2026

Last Modified

September 29, 2026

Advisory Details (1)

Auto-updated Oct 2, 2026
No fix on record yet.
Web page

XSA-468 - Xen Security Advisories

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

Vendor Advisories for CVE-2025-27463(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 9× in last 7d / 51× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. 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. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 96 of 402 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. 4 repeat rows among the latest 100 are merged into the row they repeat. The 306 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-11 20:46 UTCEG score recompute
  2. 2026-10-11 18:57 UTCEG score recompute
  3. 2026-10-11 15:34 UTCEG score recompute
  4. 2026-10-10 19:59 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  5. 2026-10-09 20:06 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  6. 2026-10-08 17:09 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  7. 2026-10-07 23:46 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  8. 2026-10-06 15:16 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  9. 2026-10-05 17:42 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  10. 2026-10-04 23:21 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  11. 2026-10-03 14:24 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  12. 2026-10-01 19:49 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  13. 2026-10-01 16:03 UTCEG score recompute
  14. 2026-10-01 16:03 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  15. 2026-09-30 15:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  16. 2026-09-29 19:25 UTCEG score recompute
  17. 2026-09-29 19:25 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  18. 2026-09-29 15:19 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  19. 2026-09-28 13:50 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  20. 2026-09-28 10:29 UTCEG score recompute
  21. 2026-09-28 10:29 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  22. 2026-09-26 15:58 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  23. 2026-09-26 00:24 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  24. 2026-09-24 14:02 UTCEPSS rescoreEPSS 0.2% · 4th percentile
  25. 2026-09-24 11:26 UTCEG score recompute
Show 71 more
  1. 2026-09-24 11:26 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  2. 2026-09-23 13:47 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  3. 2026-09-23 09:42 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  4. 2026-09-23 05:56 UTCEG score recompute
  5. 2026-09-23 05:56 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  6. 2026-09-20 20:15 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  7. 2026-09-18 19:27 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  8. 2026-09-18 10:09 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  9. 2026-09-18 05:36 UTCEG score recompute
  10. 2026-09-18 05:36 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  11. 2026-09-16 14:07 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  12. 2026-09-16 05:13 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  13. 2026-09-14 11:12 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  14. 2026-09-14 07:15 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  15. 2026-09-14 03:30 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  16. 2026-09-13 23:46 UTCEG score recompute
  17. 2026-09-13 23:46 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  18. 2026-09-13 16:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  19. 2026-09-13 16:43 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  20. 2026-09-13 12:08 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  21. 2026-09-13 08:19 UTCEG score recompute
  22. 2026-09-13 08:19 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  23. 2026-09-12 15:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  24. 2026-09-12 13:34 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  25. 2026-09-12 03:24 UTCEG score recompute
  26. 2026-09-12 03:24 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  27. 2026-09-11 14:52 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  28. 2026-09-11 09:35 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  29. 2026-09-10 09:33 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  30. 2026-09-08 21:59 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  31. 2026-09-07 16:00 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  32. 2026-09-06 13:59 UTCEG score recompute
  33. 2026-09-06 13:59 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  34. 2026-09-06 13:46 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  35. 2026-09-06 02:20 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  36. 2026-09-05 22:35 UTCEG score recompute
  37. 2026-09-05 22:35 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  38. 2026-09-04 05:05 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  39. 2026-09-02 14:11 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  40. 2026-09-01 13:53 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  41. 2026-08-31 00:10 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  42. 2026-08-30 20:26 UTCEG score recompute
  43. 2026-08-30 20:26 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  44. 2026-08-30 19:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  45. 2026-08-30 16:42 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  46. 2026-08-30 11:13 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  47. 2026-08-30 06:49 UTCEG score recompute
  48. 2026-08-30 06:48 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  49. 2026-08-30 01:21 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  50. 2026-08-28 21:40 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  51. 2026-08-28 02:42 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  52. 2026-08-27 21:45 UTCEG score recompute
  53. 2026-08-27 21:45 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  54. 2026-08-27 14:24 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  55. 2026-08-27 01:09 UTCEG score recompute
  56. 2026-08-27 01:09 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  57. 2026-08-26 14:45 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  58. 2026-08-26 12:55 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  59. 2026-08-26 08:19 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  60. 2026-08-26 03:52 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  61. 2026-08-25 15:54 UTCEG score recompute
  62. 2026-08-25 15:54 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  63. 2026-08-25 13:48 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  64. 2026-08-25 11:38 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  65. 2026-08-25 07:41 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  66. 2026-08-25 03:50 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  67. 2026-08-25 00:05 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  68. 2026-08-24 20:21 UTCEG score recompute
  69. 2026-08-24 20:21 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL
  70. 2026-08-24 14:16 UTCEPSS rescoreEPSS 0.2% · 5th percentile
  71. 2026-08-24 13:20 UTCGHSA enrichmentGHSA-j273-68h8-x289 · GitHub severity CRITICAL

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2025-27463?
CVE-2025-27463 is a critical-severity vulnerability; its CVE record was published on July 9, 2026. [This CNA information record relates to multiple CVEs; the text explains which aspects/vulnerabilities correspond to which CVE.] The Windows PV drivers expose various facilities to userspace. Several of these have no security descriptor, and are therefore fully accessible to unprivileged users.…
When was CVE-2025-27463 made public?
CVE-2025-27463 was made public on May 27, 2025: that is the date its CVE record's CNA, Xen Project, gives for when the vulnerability was made public. The CVE record itself was published on July 9, 2026. EchelonGraph's copy of the record carries a last-modified date of September 29, 2026; the record at its source may have been updated since.
Is CVE-2025-27463 actively exploited?
CVE-2025-27463 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 0.2% probability of exploitation in the next 30 days (4th percentile of EPSS-scored CVEs).
What is the CVSS score of CVE-2025-27463?
CVE-2025-27463 has a CVSS base score of 9.4 (a secondary CVSS source that NVD displays; NVD's own analysis pending).
How do I remediate CVE-2025-27463?
No fix for CVE-2025-27463 is confirmed yet. Until one is published, restrict network exposure of the affected system or apply the vendor's mitigation — for example, keep it off the internet or limit it to trusted networks — and watch the vendor's advisory for the fix. The vendor advisories EchelonGraph has for CVE-2025-27463 are linked in the Vendor Advisories panel on this page.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2025-27463

Explore →

Is Your Infrastructure Affected by CVE-2025-27463?

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

Book a Demo →Browse All CVEs