Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Obtain low-privileged local account
  2. Delivery
    Run crafted media-handling program
  3. Exploit
    Trigger use-after-free in Windows Media
  4. Execution
    Reclaim freed object with controlled data
  5. Persist
    Execute code as SYSTEM
  6. Impact
    Full host compromise

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK

2 techniques across 2 tactics: Execution, Privilege Escalation

The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up.

Exploitation Conditions

Exploitation requires the attacker to already possess authenticated, low-privileged local access to the target (CVSS PR:L, AV:L) and the ability to execute code that interacts with the Windows Media component - this is a local escalation, not a remote entry point. No user interaction is needed (UI:N) and the Windows Media component is present by default across all listed Windows 10/11 and Server 2016-2025 editions, so no non-default configuration is required to reach the vulnerable code. The primary limiting factors are the need for prior local access and a valid (even unprivileged) account; it cannot be triggered remotely or by an unauthenticated actor, which constrains it to post-compromise or malicious-insider use rather than internet-facing mass exploitation.

Impact

The signals are internally consistent and point to a real-but-not-emergency local escalation. The CVSS 3.1 vector (AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H, base 7.8 High) shows local attack vector, low complexity, low privileges required, and no user interaction, with total confidentiality/integrity/availability impact on the unchanged scope - classic local EoP to SYSTEM. Corroborating this, CISA SSVC rates Technical Impact as 'total' but Automatable as 'no' and Exploitation as 'none', and EPSS is low at 0.25% (16th percentile), so there is no evidence of active exploitation or mass automation. There is no KEV listing and no POC identified. The practical priority is driven by prevalence and the fact that local EoPs are frequently chained after initial access, not by imminent mass exploitation. No key signals conflict - the vector's local scope aligns with the description's 'elevate privileges locally' and the 'authorized attacker' language aligns with PR:L.

Exploit ScenarioDerived

An attacker who has already obtained a standard, low-privileged account on a Windows host - for example via phishing, a stolen credential, or a compromised service - runs a crafted program that manipulates the Windows Media component's heap to trigger the use-after-free, reclaiming the freed object with controlled data. By steering the dangling-pointer dereference into code execution, the attacker elevates from their limited context to SYSTEM, gaining full control of the machine. No public exploit code has been identified at time of analysis, and the low complexity (AC:L) means a working exploit, once developed, would be reliable.

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

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

Alert me

AnalysisAIv2 – Jul 20, 2026

Local privilege escalation in the Windows Media component across Windows 10, Windows 11, and Windows Server (2016 through 2025) allows an authenticated low-privileged attacker to elevate to SYSTEM by exploiting a use-after-free memory corruption flaw. Microsoft has released patches and reports no public exploit identified at time of analysis; EPSS is low at 0.25% and CISA SSVC records exploitation status as 'none', though technical impact is rated total. Given the ubiquity of the Windows Media stack, this is a routine but broadly applicable Patch-Tuesday-class local EoP.

Earlier versions of this analysis (1)
v1 Jul 14, 2026 - 21:29 CVSS 7.0

Local privilege escalation in the Windows Media component affects a broad range of Microsoft Windows client and server editions (Windows 10 1607 through Windows 11 26H1, and Windows Server 2016 through 2025). A low-privileged authenticated attacker can abuse a use-after-free (CWE-416) memory corruption flaw to elevate to higher privileges, achieving full confidentiality, integrity, and availability impact. There is no public exploit identified at time of analysis and the flaw is not on CISA KEV, but the high attack complexity (a likely race condition) is the main barrier to reliable exploitation.

RemediationAI

Apply the Microsoft cumulative security update that raises each affected build to at least the fixed version for its release train - Vendor-released patch: Windows 10 1607/Server 2016 build 10.0.14393.9339, Windows 10 1809/Server 2019 build 10.0.17763.9020, Windows 10 21H2 build 10.0.19044.7548, Windows 10 22H2 build 10.0.19045.7548, Windows Server 2022 build 10.0.20348.5386, Windows 11 24H2 build 10.0.26100.8875, Windows 11 25H2 build 10.0.26200.8875, Windows 11 26H1 build 10.0.28000.2269, and Windows Server 2025 build 10.0.26100.33158; consult the MSRC guidance at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-50358 to map your OS to the exact KB. Because exploitation requires an existing authenticated local foothold, interim compensating controls center on limiting who can run code on the host: enforce least privilege and restrict interactive/local logon rights so untrusted users cannot execute code, apply application control (WDAC/AppLocker) to block untrusted binaries, and monitor for anomalous media-handling process behavior; these reduce opportunity but do not remove the flaw, and application-control policies can break legitimate media workflows if scoped too broadly, so patching remains the only complete fix.

Affected VersionsENISA

Windows Server 2025 10.0.26100.0 <10.0.26100.33158
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33158
Windows 10 Version 1809 10.0.17763.0 <10.0.17763.9020
Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9339
Windows 10 Version 1607 10.0.14393.0 <10.0.14393.9339
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.2269
Windows Server 2016 10.0.14393.0 <10.0.14393.9339
Windows Server 2019 10.0.17763.0 <10.0.17763.9020
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.8875
Windows 10 Version 22H2 10.0.19045.0 <10.0.19045.7548
Windows Server 2022 10.0.20348.0 <10.0.20348.5386
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9020
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.8875
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7548

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9339
euvd windows_10_version_1809 fix: 10.0.17763.9020
euvd windows_10_version_21h2 fix: 10.0.19044.7548
euvd windows_10_version_22h2 fix: 10.0.19045.7548
euvd windows_11_version_24h2 fix: 10.0.26100.8875
euvd windows_11_version_25h2 fix: 10.0.26200.8875
euvd windows_11_version_26h1 fix: 10.0.28000.2269
euvd windows_server_2016 fix: 10.0.14393.9339
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9339
euvd windows_server_2019 fix: 10.0.17763.9020
euvd windows_server_2019_server_core_installation fix: 10.0.17763.9020
euvd windows_server_2022 fix: 10.0.20348.5386
euvd windows_server_2025 fix: 10.0.26100.33158
euvd windows_server_2025_server_core_installation fix: 10.0.26100.33158

Source: OSV (Open Source Vulnerabilities)

Affects your stack

Affects 14 packages in euvd

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

Technical ContextAI · show details

The flaw is a CWE-416 use-after-free in the Windows Media subsystem - the set of libraries and kernel/user-mode components that handle media parsing, decoding, and playback within Windows. A use-after-free occurs when code continues to reference a heap object after it has been freed; an attacker who can control heap allocation timing can reclaim the freed memory with attacker-controlled data and force the dangling pointer to operate on that data, yielding memory corruption that can be steered into arbitrary code execution in the security context of the affected component. The CPE data confirms the affected surface is the Microsoft Windows platform itself (windows_10_version_1607 through windows_11_version_26h1, plus Windows Server 2016/2019/2022/2025 including Server Core installations), meaning this is an OS-level component present in virtually every Windows install rather than a standalone application.

Know when Windows Server 2016 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 HIGH
NVD 7.8 HIGH
AV:L/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:H
vuln.today AI 7.8 HIGH

Local vector and low-privileged account required (AV:L, PR:L); no user interaction; a use-after-free to SYSTEM yields total confidentiality, integrity, and availability impact.

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

Primary rating from Vendor (microsoft).

CVSS VectorNVD

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

Lifecycle Timeline

2
CVSS changed
Jul 20, 2026 - 17:37 NVD
7.0 (HIGH) 7.8 (HIGH)
CVE Published
Jul 14, 2026 - 17:06 cve.org
HIGH 7.0

DescriptionNVD

Use after free in Windows Media allows an authorized attacker to elevate privileges locally.

Executive ViewAI

Why It Matters

A local privilege escalation vulnerability (CVE-2026-50358) in Windows Media affects Windows 10, Windows 11, and Windows Server installations across your enterprise. Any authenticated user with standard system access could escalate to administrative privileges, enabling unauthorized data access, lateral movement, or malware installation. While technically rated HIGH severity with broad platform coverage, real-world exploitation probability remains low and no active attacks have been documented, enabling controlled patching through standard update windows.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.3%
Top 84% exploitable
Prevalence
Ubiquitous
Core Windows OS component present in nearly all Windows environments
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.3%
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
Scheduled
Exploitation
None
System Exposure· derived
Small
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +39
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

Attack Technique

Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.

Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.

Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.

CVE-2021-40444 HIGH POC
8.8 Sep 15

Windows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX

CVE-2021-34527 HIGH POC
8.8 Jul 02

<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi

CVE-2022-30190 HIGH POC
7.8 Jun 01

Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f

CVE-2017-0147 HIGH POC
7.5 Mar 17

The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows

CVE-2018-8174 HIGH POC
7.5 May 09

The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co

CVE-2021-1675 HIGH POC
7.8 Jun 08

Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth

CVE-2016-7255 HIGH POC
7.8 Nov 10

The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited

CVE-2023-36884 HIGH POC
7.5 Jul 11

Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo

CVE-2023-44487 HIGH POC
7.5 Oct 10

Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour

CVE-2024-30088 HIGH POC
7.0 Jun 11

Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR

CVE-2019-1458 HIGH POC
7.8 Dec 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

CVE-2018-8453 HIGH POC
7.8 Oct 10

An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in

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