Xen Hypervisor
CVE-2025-58147
HIGH
Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessGain control of a guest VM
-
ExploitIssue crafted hypercall/operation
-
ExecutionTrigger out-of-bounds read in Xen
-
ImpactLeak host or co-tenant memory
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, read limits
MITRE ATT&CK
1 technique across 1 tactic: Collection The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation realistically requires the attacker to control or run code inside a guest VM on an affected Xen host (multi-tenant or untrusted-guest deployments) and to invoke the specific vulnerable code path to trigger the out-of-bounds read; exact triggering conditions are defined in XSA-475, which is not reproduced in the provided description. Limiting factors: single-tenant hosts with no untrusted guests face minimal exposure; impact is confidentiality-only (no integrity or availability effect), and the supplied CVSS claim of remote unauthenticated (AV:N/PR:N) access is not corroborated and likely requires guest-level access in practice. Affected versions precede Xen 4.20.1 / Alpine package 4.20.1-r2. |
| Impact | Signals are mixed and point to a moderate, non-urgent priority. The supplied CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N, base 7.5) describes a remote, unauthenticated, confidentiality-only information disclosure (CWE-125, out-of-bounds read). However, this vector is questionable for a Xen hypervisor flaw: XSA-475 class issues are almost always triggered by a malicious or cooperative guest VM (local vector, attacker-controlled guest = PR:L), not by an anonymous network attacker - VERIFY WITH VENDOR, as AV:N/PR:N likely overstates reachability. The exploitation-probability signals are low and consistent with each other: EPSS is 0.36% (28th percentile), there is NO CISA KEV listing, and no public exploit was identified, so this is not evidence of active or imminent widespread exploitation. Net: a legitimate confidentiality bug worth patching on normal hypervisor-maintenance cadence, but not a drop-everything issue - and the headline 7.5 'network' score probably overstates real-world exposure for a hypervisor memory-disclosure flaw. |
| Exploit ScenarioDerived | An attacker who controls a guest VM on a shared Xen host issues a crafted operation/hypercall that triggers an out-of-bounds read in the hypervisor, causing it to return adjacent memory contents that may belong to the host or other tenants. The leaked data could expose secrets (keys, memory from co-located guests) useful for further attacks. No public exploit code was identified, so exploitation currently requires original research into XSA-475. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 19, 2026
Out-of-bounds read in the Xen hypervisor (CVE-2025-58147) can let an attacker who controls or runs code inside a guest VM on an affected host read hypervisor memory, exposing confidential data. Exploitation is assessed as local, high-complexity, and requiring low privileges (CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N), with confidentiality-only impact; the supplied remote unauthenticated 7.5 score is not corroborated. No public exploit identified at time of analysis, EPSS is low at 0.36% (28th percentile), and Alpine has released a fix in xen 4.20.1-r2 per XSA-475.
RemediationAI
Vendor-released patch: Alpine Linux xen 4.20.1-r2, incorporating the upstream Xen fix for XSA-475. Upgrade the Alpine xen package to 4.20.1-r2 or later and plan a hypervisor host restart, since Xen package updates generally require a reboot to activate. If immediate upgrade is not possible, reduce exposure by not running untrusted or multi-tenant guest VMs on affected hosts and by restricting who can create or control guests, because the assessed attack path requires guest-level access; these are compensating controls only and do not remove the bug. Consult XSA-475 at https://xenbits.xenproject.org/xsa/advisory-475.html and the Alpine package changelog for exact deployment guidance.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Xen is a type-1 hypervisor that isolates guest virtual machines from the host and from each other. CWE-125 identifies the root cause as an out-of-bounds read, meaning the vulnerable code path can read beyond the intended memory boundary and disclose hypervisor memory contents. The authoritative assessed vector is AV:L/AC:H/PR:L/UI:N/S:C/C:H/I:N/A:N, which indicates an attacker with low privileges and local access, likely through control of a guest VM, high attack complexity, a scope change, and a confidentiality-only impact; integrity and availability are not affected. The NVD-style CVSS 7.5 AV:N/AC:L/PR:N/UI:N score describes remote unauthenticated access, but that is not corroborated by the assessed exploitation conditions and should not be used to justify internet-facing or unauthenticated exposure assumptions. The provided CPE cpe:2.3:o:xen:xen:*:*:*:*:*:*:*:* identifies the Xen product family but is version-wildcarded, so affectedness must be scoped by the vendor fix: Alpine xen before 4.20.1-r2 and upstream Xen before 4.20.1.
Know when Xen gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N
Guest-triggered hypervisor OOB read needs attacker-controlled guest (AV:L/PR:L) and specific conditions (AC:H); it crosses the VM boundary to leak host/other-guest memory (S:C, C:H), with no I/A impact.
Primary rating from Vendor (vendor:alpine).
CVSS VectorVendor: vendor:alpine
Lifecycle Timeline
3DescriptionCVE.org
Alpine Linux: xen fixed in 4.20.1-r2
Executive ViewAI
Xen hypervisor hosts carry a confidentiality exposure that could let a low-privileged user inside a guest VM read hypervisor memory, potentially revealing sensitive data across virtualized workloads. Exploitation is local and high-complexity, and no public exploit identified at time of analysis; vendor-released patch: xen 4.20.1-r2. Leadership should prioritize multi-tenant and highest-value virtualization estates because a successful attack could weaken tenant isolation and trust.
Apply vendor patch.
Threat Intelligence Overview
NVD
CVE.org
EPSS
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Affected Products (CPE)CVE.org
The x86-64 kernel system-call functionality in Xen 4.1.2 and earlier, as used in Citrix XenServer 6.0.2 and earlier and
The Floppy Disk Controller (FDC) in QEMU, as used in Xen 4.5.x and earlier and KVM, allows local guest users to cause a
A statement in the System Programming Guide of the Intel 64 and IA-32 Architectures Software Developer's Manual (SDM) wa
The AdSanity plugin for WordPress is vulnerable to arbitrary file uploads due to missing file type validation in the 'aj
An issue was discovered in Xen through 4.9.x allowing x86 PV guest OS users to cause a denial of service (unbounded recu
An issue (known as XSA-212) was discovered in Xen, with fixes available for 4.8.x, 4.7.x, 4.6.x, 4.5.x, and 4.4.x. Rated
The C+ mode offload emulation in the RTL8139 network card device model in QEMU, as used in Xen 4.5.x and earlier, allows
Xen, when used on a system providing PV backends, allows local guest OS administrators to cause a denial of service (hos
x86 pv: Insufficient care with non-coherent mappings T[his CNA information record relates to multiple CVEs; the text exp
Xen through 4.8.x does not validate memory allocations during certain P2M operations, which allows guest OS users to obt
Xen through 4.8.x mishandles page transfer, which allows guest OS users to obtain privileged host OS access, aka XSA-217
The grant-table feature in Xen through 4.8.x does not ensure sufficient type counts for a GNTMAP_device_map and GNTMAP_h
GitHub PoC
Exploit-DB