Skip to main content

Windows Hyper-V EUVDEUVD-2026-99378

| CVE-2026-83839 HIGH
Time-of-check Time-of-use (TOCTOU) Race Condition (CWE-367)
2026-10-13 secure@microsoft.com GHSA-72mw-639j-fvxf
7.0
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Obtain low-privileged local access on Hyper-V host
  2. Delivery
    Repeatedly invoke vulnerable Hyper-V operation
  3. Exploit
    Win TOCTOU race between check and use
  4. Execution
    Execute code with SYSTEM privileges
  5. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture TOCTOU prevention
Exploitation Conditions

Requires the Windows Hyper-V role to be installed/enabled on the host and an attacker with an existing low-privileged authenticated local account or local code-execution foothold (PR:L, AV:L). Exploitation hinges on winning a time-of-check-to-time-of-use race condition (CWE-367), reflected in AC:H, meaning success is probabilistic and may require many attempts and precise timing; no user interaction is needed (UI:N). Limiting factors: no network vector (local only), high attack complexity from the race window, prerequisite valid local privileges, and applicability only to the listed unpatched Windows 10/11 and Windows Server 2019-2025 builds with Hyper-V present.

Impact

This is a legitimate but not top-tier priority. The CVSS 3.1 vector (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.0 HIGH) describes a local elevation-of-privilege flaw requiring existing low-privileged access and a high-complexity race window, yielding full confidentiality, integrity, and availability impact on the host. No EPSS score, CISA KEV listing, or public POC is present in the provided data, so there is no evidence of active or imminent exploitation; the attack vector is local and AC:H (winning a TOCTOU timing race) materially raises the bar for reliable exploitation. A SSVC-style read: exploitation status appears 'none' (no KEV/POC signal), automatable is 'no' (local, race-dependent, not internet-reachable at scale), and technical impact is 'total' (C/I/A all High). Note a metadata conflict to verify: the input Tags include 'Information Disclosure', but the description and CWE-367 (TOCTOU) describe privilege escalation with full C/I/A impact, not a disclosure-only issue - treat the 'Information Disclosure' label as suspect. Overall this is a patch-in-normal-cycle EoP on Hyper-V hosts, elevated in importance only where multi-tenant virtualization or strict host isolation is a security boundary.

Exploit ScenarioDerived

A low-privileged user or a compromised guest-adjacent process already present on a Windows host running the Hyper-V role repeatedly triggers a Hyper-V operation while manipulating the underlying resource between the check and the use, winning the TOCTOU race to gain SYSTEM-level privileges on the host. Because the attack is local (AV:L) and high-complexity (AC:H), it requires an existing foothold and many race attempts rather than remote delivery. No public exploit code was identified in the provided data.

This Week Schedule remediation this week. Why: HIGH severity (CVSS 7.0-8.9).
Patch available 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – Oct 13, 2026

Local privilege elevation in Windows Hyper-V allows an attacker who already holds a low-privileged account or code-execution foothold on the host to win a time-of-check-to-time-of-use race condition and obtain high-integrity code execution. The issue affects unpatched Windows 10 21H2/22H2, Windows 11 23H2 through 26H1, and Windows Server 2019, 2022, and 2025 builds wherever the Hyper-V role is installed, and is scored CVSS 3.1 7.0 (AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H) - local-only access, existing privileges required, and a narrow race window that makes success probabilistic and likely to need many attempts. No public exploit has been identified at time of analysis and the flaw is not confirmed as actively exploited (no CISA KEV listing), but a vendor patch is available and should be applied as routine maintenance.

RemediationAI

Apply the vendor-released fixes listed in the Microsoft MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83839): Windows 10 1809 and Windows Server 2019 to build 10.0.17763.9376, Windows 10 21H2/22H2 to 10.0.19044.7807, Windows 11 23H2 to 10.0.22631.7652, Windows 11 24H2 to 10.0.26100.9711, Windows 11 25H2 to 10.0.26200.9711, Windows 11 26H2 to 10.0.26300.9711, Windows 11 26H1 to 10.0.28000.3231, Windows Server 2022 to 10.0.20348.5761, and Windows Server 2025 to 10.0.26100.33650; patch status is confirmed as available from the vendor, so prioritise hosts that both run Hyper-V and permit non-administrative local logon. Until patching completes, the most effective compensating control is to remove unnecessary accounts from the Hyper-V Administrators group and to restrict interactive local logon and low-privileged code execution on Hyper-V hosts, with the trade-off that affected users lose the ability to manage virtual machines and virtual switches. On hosts that do not genuinely require virtualization, disable the Hyper-V role and its dependent features - a trade-off that breaks VMs, Windows Sandbox, WSL2, containers, and typically virtualization-based security such as Credential Guard and HVCI, so it should only be considered where those workloads are expendable. Because exploitation depends on winning a race window (CWE-367, AC:H), rate-limiting or monitoring repeated rapid Hyper-V management API activity may raise the cost of brute-forcing the window, but no configuration change reliably closes a TOCTOU defect and this should be treated as detection rather than prevention; there is no confirmed public exploit to signature against at this time, so build detections around anomalous process integrity transitions on Hyper-V hosts instead.

Affected VersionsENISA

Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows 11 Version 23H2 10.0.22631.0 <10.0.22631.7652
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9376
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807

Affected Packages

euvd windows_10_version_1809 fix: 10.0.17763.9376
euvd windows_10_version_21h2 fix: 10.0.19044.7807
euvd windows_10_version_22h2 fix: 10.0.19044.7807
euvd windows_11_version_23h2 fix: 10.0.22631.7652
euvd windows_11_version_24h2 fix: 10.0.26100.9711
euvd windows_11_version_25h2 fix: 10.0.26200.9711
euvd windows_11_version_26h1 fix: 10.0.28000.3231
euvd windows_11_version_26h2 fix: 10.0.26300.9711
euvd windows_server_2019 fix: 10.0.17763.9376
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9376
euvd windows_server_2022 fix: 10.0.20348.5761
euvd windows_server_2025 fix: 10.0.26100.33650
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33650

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 13 packages in euvd

Checking this CVE against your own stacks and servers is part of the Basic plan and up.

Technical ContextAI · show details

Hyper-V is Microsoft's Type-1 hypervisor, whose kernel-mode components manage partitions, virtual processors, memory (GPA/SPA) mappings, VMBus channels, and emulated/synthetic devices, arbitrating between the parent (host) partition and child (guest) partitions. CVE-2026-83839 is rooted in CWE-367, Time-of-Check Time-of-Use: a security-relevant property of a resource (for example a handle, object reference, or memory descriptor) is validated at one point in the hypervisor's control path and then relied upon later, leaving a window in which a local caller can alter the underlying state so that the validated property no longer holds at the moment of use. The resulting access-control bypass lets the caller act with higher integrity than their token should permit, which is why the assessed vector shows high impact on confidentiality, integrity, and availability (C:H/I:H/A:H) with scope unchanged (S:U) - the escalation stays within the host's security boundary. Notably, this is a host-side local vector (AV:L), not a guest-to-host escape path (which would be AV:A or AV:N), so it targets an attacker operating on the Hyper-V host itself rather than from inside a virtual machine; the AC:H rating reflects the timing sensitivity inherent in exploiting a race window, and UI:N indicates no victim interaction is required. No CPE strings were supplied with the intelligence, so mapping is based on the EUVD build ranges for Windows 10, Windows 11, and Windows Server editions that ship Hyper-V.

Know when Hyper-V 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

Vendor (microsoft) PRIMARY 7.0 HIGH
AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.0 HIGH

Local TOCTOU race needing an existing low-privileged foothold gives AV:L/PR:L and AC:H for the timing window; successful host privilege escalation yields full C/I/A.

3.1 AV:L/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:H
4.0 AV:L/AC:L/AT:P/PR:L/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.0

DescriptionCVE.org

Time-of-check time-of-use (toctou) race condition in Windows Hyper-V allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

Microsoft Windows Hyper-V hosts are affected by a high-severity local privilege-elevation flaw that could let an attacker with an existing low-level foothold on the host gain high-integrity code execution. Organizations running affected Windows 10, Windows 11, and Windows Server builds with the Hyper-V role should treat this as a priority patching item because a compromised virtualization host can undermine workload isolation and administrative control. There is no public exploit identified at time of analysis, but the vendor patch is available and should be applied as routine maintenance.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.2%
Top 92% exploitable
Prevalence
High
Hyper-V is a widely deployed Windows Server/enterprise virtualization role
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 sources
Confidence: Medium

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.

SignalValue
Severity HIGH
CISA KEV No
Public POC No
EPSS 0.2%
Patch available Yes
Active threat No
Deciding rule
HIGH severity (CVSS 7.0-8.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision
Defer
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

35
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +35
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0
CVE-2026-83716 HIGH
8.8 Oct 13

Heap-based buffer overflow in Microsoft Hyper-V (CVE-2026-83716, CVSSv3.1 8.8) lets an authenticated attacker who alread

CVE-2026-21255 HIGH
8.8 Feb 10

Windows Hyper-V fails to properly enforce access controls, enabling local authenticated users to circumvent security fea

CVE-2026-85369 HIGH
8.2 Oct 13

Elevation of privilege in Microsoft Hyper-V lets an attacker who already holds high privileges inside a guest virtual ma

CVE-2026-87705 HIGH
7.4 Oct 13

Hyper-V on affected Windows and Windows Server hosts fails to properly verify the source of a communication channel, let

CVE-2026-21247 HIGH
7.3 Feb 10

Improper input validation in Windows Hyper-V allows an authorized attacker to execute code locally. [CVSS 7.3 HIGH]

CVE-2026-21248 HIGH POC
7.3 Feb 10

Heap overflow in Windows Hyper-V enables authenticated local users to achieve arbitrary code execution with high privile

CVE-2026-21244 HIGH POC
7.3 Feb 10

Heap overflow in Windows Hyper-V enables authenticated local users to achieve arbitrary code execution with high privile

CVE-2026-108399 HIGH
7.2 Oct 13

Local privilege escalation in Windows Hyper-V allows an authorized attacker with high privileges on a host where the Hyp

CVE-2026-83671 MEDIUM
6.5 Oct 13

An out-of-bounds read in the Microsoft Hyper-V virtualization stack allows a locally positioned attacker holding low pri

CVE-2026-83766 MEDIUM
4.2 Oct 13

Incorrect authorization in Windows Hyper-V (CWE-863) on multiple Windows 10, Windows 11, and Windows Server versions cou

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy