CVE-2025-48807: Windows Hyper-V Remote Code Execution Vulnerability

Overview

Severity

Medium (CVSS 6.7)

CVSS Vector

CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C

Category

Remote Code Execution

Exploit Status

Not Exploited

Exploitation Likelihood

Less Likely

Patch Tuesday

2025-Aug

Released

2025-08-12

Last Updated

2025-09-09

EPSS Score

0.07% (percentile: 20.8%)

Description

Improper restriction of communication channel to intended endpoints in Windows Hyper-V allows an authorized attacker to execute code locally.

FAQ

According to the CVSS metric, the attack complexity is high (AC:H). What does that mean for this vulnerability? A race condition is triggered when the admin begins administering from the host system and not a guest or nested guest. According to the CVSS metric, the attack vector is local (AV:L). Why does the CVE title indicate that this is a remote code execution? The word Remote in the title refers to the location of the attacker. This type of exploit is sometimes referred to as Arbitrary Code Execution (ACE). The attack itself is carried out locally. The vulnerable endpoint is only available over the local VM interface as all external communication is blocked. This means an attacker needs to execute code from the local machine to exploit the vulnerability. According to the CVSS metric, user interaction is required (UI:R) and privileges required is Low (PR:L). What does that mean for this vulnerability? At the time the authorized attacker sends a specially crafted request an administrator needs to take action on the host. According to the CVSS metric, successful exploitation could lead to a scope change (S:C). What does this mean for this vulnerability? An attacker on a nested guest VM who successfully exploited the vulnerability could escape their VM and gain admin privilege on the guest that is serving as the host. For diagrams and more detailed information about nested VMs please see Run Hyper-V in a Virtual Machine with Nested Virtualization.

Affected Products (19)

Windows

• Windows 10 Version 1809 for x64-based Systems
• Windows Server 2019
• Windows Server 2019 (Server Core installation)
• Windows Server 2022
• Windows Server 2022 (Server Core installation)
• Windows 10 Version 21H2 for x64-based Systems
• Windows Server 2025 (Server Core installation)
• Windows 11 Version 23H2 for ARM64-based Systems
• Windows 11 Version 23H2 for x64-based Systems
• Windows Server 2022, 23H2 Edition (Server Core installation)
• Windows 11 Version 24H2 for ARM64-based Systems
• Windows 11 Version 24H2 for x64-based Systems
• Windows Server 2025
• Windows 10 Version 1607 for x64-based Systems
• Windows Server 2016
• Windows Server 2016 (Server Core installation)

ESU

• Windows 11 Version 22H2 for ARM64-based Systems
• Windows 11 Version 22H2 for x64-based Systems
• Windows 10 Version 22H2 for x64-based Systems

Security Updates (9)

• 5065428
• 5065432
• 5065306
• 5065429
• 5065431
• 5065426
• 5065474
• 5065425
• 5065427

Acknowledgments

QWangWang & zcgonvh

Revision History

• 2025-08-12: Information published. This CVE was addressed by updates that were released in July 2025, but the CVE was inadvertently omitted from the July 2025 Security Updates. This is an informational change only. Customers who have already installed the July 2025 updates do not need to take any further action.
• 2025-09-09: To comprehensively address CVE-2025-48807, Microsoft has released September 2025 security updates for the following versions of Windows: Windows Server 2016 and newer, x64-based editions of Windows 10 Version 1607 and Windows 10 Version 1809, and all supported versions of Windows 10 Version 21H2 and newer and Windows 11 Version 22H2 and newer. Microsoft recommends that customers install the update to be fully protected from the vulnerability. Customers whose systems are configured to receive automatic updates do not need to take any further action.