Skip to main content
View

Attack ChainAIDerived

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

  1. Access
    Host malicious media file on web/email
  2. Delivery
    Victim opens file in Windows Media Player
  3. Exploit
    Trigger heap buffer overflow in media parser
  4. Execution
    Corrupt heap and hijack control flow
  5. Impact
    Execute arbitrary code in user context

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Heap buffer bounds checking
MITRE ATT&CK

1 technique across 1 tactic: Execution

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

Exploitation Conditions

Exploitation requires Windows Media Player to process attacker-supplied media content (a crafted file or network stream) that triggers the heap overflow in the media-parsing path; the affected component is present on essentially all listed Windows 10/11 and Windows Server builds below the patched version. The vendor vector asserts no privileges and no user interaction (PR:N/UI:N), but in practice a victim typically must open or play the malicious media, which is the primary real-world limiting factor along with the requirement that Windows Media Player be the handler for the delivered content; applying the available Microsoft patch removes the condition.

Impact

The provided CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, base 9.8) describes a maximally dangerous remote, unauthenticated, no-interaction RCE with total confidentiality, integrity, and availability impact. However, this conflicts with the nature of the product: Windows Media Player heap overflows are almost always triggered by parsing a crafted media file or stream, which realistically implies user interaction (opening/playing the file) - verify the UI:N claim against the Microsoft advisory. The SSVC decision framework tempers the raw severity: Exploitation is rated 'none' (no observed exploitation), Automatable is 'yes' (consistent with network-reachable parsing of attacker-supplied content), and Technical Impact is 'total' (aligning with C:H/I:H/A:H). This is NOT in CISA KEV and no POC is referenced, so exploitation status is 'no public exploit identified at time of analysis'. No EPSS score was supplied, so widespread-exploitation probability cannot be quantified. Net assessment: genuinely high-priority because it affects a component present across virtually all supported Windows builds and a patch is available, but the absence of KEV/POC/EPSS and the likely need for a victim to open malicious media suggest it is a patch-promptly rather than drop-everything emergency.

Exploit ScenarioDerived

An attacker crafts a malicious media file or stream that triggers a heap-based buffer overflow when processed by Windows Media Player, delivering it via a web page, email attachment, or shared link. When the content is opened/played, the overflow corrupts heap memory and the attacker gains arbitrary code execution in the user's context. No public exploit code is identified at time of analysis, and no active exploitation is recorded (CISA SSVC Exploitation: none).

Act Now Prioritize within 24-48h. Why: CRITICAL severity.
Patch available 0.7% exploitation probability (EPSS)

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

Alert me

AnalysisAIv1 – Oct 13, 2026

Heap-based buffer overflow in Microsoft Windows Media Player enables remote code execution when the component processes attacker-supplied media content such as a crafted file or network stream. The vendor scoring places this at CVSS 3.1 9.8 (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H), describing unauthenticated, no-interaction compromise with total confidentiality, integrity, and availability impact; the affected parsing library ships on essentially every Windows 10, Windows 11, and Windows Server build listed below the patched revision, so the exposed install base is extremely broad. No public exploit code has been identified at time of analysis and CISA's SSVC assessment records Exploitation: none, while also flagging the flaw as Automatable: yes with Technical Impact: total, meaning exploitation is expected to be trivially repeatable once a working input is produced. The primary practical gating factor is that a victim must open or play the malicious media, so the assessed real-world vector is UI:R even though the vendor vector claims UI:N.

RemediationAI

Vendor-released patch is available and should be applied as the primary fix; upgrade each affected build to at least its fixed revision, for example Windows 11 24H2 to 10.0.26100.9711, Windows 11 23H2 to 10.0.22631.7652, 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 10 21H2/22H2 to 10.0.19044.7807, Windows 10 1809 to 10.0.17763.9376, Windows 10 1607 to 10.0.14393.9612, Windows Server 2022 to 10.0.20348.5761, Windows Server 2025 to 10.0.26100.33650, Windows Server 2019 to 10.0.17763.9376, Windows Server 2016 to 10.0.14393.9612, Windows Server 2012 R2 to 6.3.9600.23470, and Windows Server 2012 to 6.2.9200.26434, using the Microsoft update guide at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-96096. If patching must be deferred, reduce exposure by removing the Windows Media Player Legacy optional feature where playback is not required (this can break legacy media playback and any application that depends on WMP components), removing .wmv/.avi/.asf/.mp3 and related file associations from Windows Media Player so a more isolated player becomes the default handler, and blocking execution of wmplayer.exe via AppLocker or WDAC on managed endpoints (expect breakage for users who legitimately rely on WMP or on applications that launch it programmatically). On servers, restrict inbound delivery of untrusted media and network streams to the host, and on Server Core installs confirm whether the media components are present at all before assuming exposure. Note that SSVC rates Automatable: yes with Technical Impact: total, so once a working media sample is available the exploit is expected to be reliably and repeatedly usable, which argues for treating the patch cadence as urgent rather than discretionary.

Affected VersionsENISA

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

Affected Packages

euvd windows_10_version_1607 fix: 10.0.14393.9612
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_2012 fix: 6.2.9200.26434
euvd windows_server_2012_r2 fix: 6.3.9600.23470
euvd windows_server_2012_r2_server_core_installation fix: 6.3.9600.23470
euvd windows_server_2012_server_core_installation fix: 6.2.9200.26434
euvd windows_server_2016 fix: 10.0.14393.9612
euvd windows_server_2016_server_core_installation fix: 10.0.14393.9612
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 20 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 root cause is a heap-based buffer overflow (CWE-122) in the media-parsing path that Windows Media Player uses to decode container and stream data. CWE-122 occurs when a program writes more data into a heap-allocated buffer than was allocated for it, corrupting adjacent heap metadata and control structures; in a media parsing context the size calculation is typically derived from attacker-controlled header or frame fields, so a malformed file or stream can be used to overwrite heap memory and redirect execution flow. Because the vulnerable code sits in a shared Windows media component, the exposure is tied to the Windows build rather than to a standalone application package, which is why the affected set from ENISA EUVD spans the Windows 10 servicing branches (1607 through 22H2), Windows 11 23H2/24H2/25H2/26H1/26H2, and Windows Server 2012, 2012 R2, 2016, 2019, 2022, and 2025, including Server Core installations. No CPE strings were supplied with the data provided, so exact platform identification should be confirmed against the Microsoft Security Response Center update guide entry referenced for this CVE. Successful exploitation in the parsing path yields arbitrary code execution in the context of the process handling the media, which for interactive playback is the logged-on user and for any server-side or automated media handling could be a higher-privileged service context.

Know when Windows 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 9.8 CRITICAL
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
ENISA EUVD HIGH
vuln.today AI 8.8 HIGH

Media Player overflows are triggered by opening attacker-supplied media, so UI:R; content is deliverable remotely (AV:N), needs no auth (PR:N), and yields full code execution (C/I/A:H).

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

Primary rating from Vendor (microsoft).

CVSS VectorVendor: microsoft

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
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:21 cve.org
CRITICAL 9.8

DescriptionCVE.org

Heap-based buffer overflow in Windows Media Player allows an unauthorized attacker to execute code over a network.

Executive ViewAI

Why It Matters

Microsoft Windows Media Player, a default component on virtually all supported Windows 10, Windows 11, and Windows Server installations, contains a critical heap-based buffer overflow that permits unauthenticated remote code execution when processing malicious media content. With no public exploit identified at time of analysis, the immediate risk is potential widespread compromise across the organization's Windows estate if a user opens a crafted file or stream. Leadership should treat this as a high-priority patching effort because successful exploitation could lead to full system control, data theft, and service disruption.

Business Impact: Severe
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
0.7%
Top 49% exploitable
Prevalence
Ubiquitous
Media Player component ships with nearly all supported Windows editions
Threat Intel
1
1 sources
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
6 sources
Confidence: High

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 CRITICAL
CISA KEV No
Public POC No
EPSS 0.7%
Patch available Yes
Active threat No
Deciding rule
CRITICAL severity
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
Open
Automatable
Yes
Human Impact
Very High
Technical Impact
Total

Priority Score

55
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +49
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: +5

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.

A heap overflow occurs when a program writes data beyond the bounds of a buffer allocated in the heap memory region.

CVE-2025-52691 CRITICAL POC
10.0 Dec 29

Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio

CVE-2019-0803 HIGH POC
7.8 Apr 09

Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in

CVE-2020-1472 MEDIUM POC
5.5 Aug 17

A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr

CVE-2025-33053 HIGH POC
8.8 Jun 10

Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables

CVE-2025-33073 HIGH POC
8.8 Jun 10

Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker

CVE-2025-13315 CRITICAL POC
9.3 Nov 19

Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b

CVE-2013-10047 CRITICAL POC
9.3 Aug 01

An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote

CVE-2012-10030 CRITICAL POC
9.3 Aug 05

FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit

CVE-2025-34101 CRITICAL POC
9.3 Jul 10

Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio

CVE-2025-13316 HIGH POC
8.2 Nov 19

Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred

CVE-2025-34095 CRITICAL POC
9.3 Jul 10

Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/

CVE-2025-11953 CRITICAL POC
9.8 Nov 03

React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo

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