CVE-2026-58542
Windows Media Remote Code Execution Vulnerability
No known exploitation. EPSS puts it in the 27th percentile. A vendor fix is available.
What to do
The vendor has published a fix. Version details are below where the sources state them.
Steps
Written by AI from the record- Check whether your organization uses Windows Media features on Windows 11 and/or Windows Server 2025 (especially any setups that may trigger Windows Media processing).
- Verify your current OS build against the fixed builds listed by Microsoft for CVE-2026-58542.
- Update Windows 11 to one of: 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2269 (whichever matches your branch), or later.
- Update Windows Server 2025 to 10.0.26100.33158 (or later).
- If you cannot immediately patch, restrict who can access the affected Windows machines in ways that would allow an attacker to induce the Windows Media behavior, and prioritize installing the Microsoft fix as soon as possible.
What it is
From the CVE record
Heap-based buffer overflow in Windows Media allows an unauthorized attacker to execute code locally.
In plain language
Written by AI from the recordCVE-2026-58542 is a Windows Media security flaw that can let a nearby attacker run code on Windows 11 or Windows Server 2025; most small businesses should act quickly because it requires getting the attacker close but it can still lead to full system compromise once triggered.
CVE-2026-58542 is a heap-based buffer overflow in Windows Media that enables local remote code execution with no prior login, requiring the attacker to be able to induce the vulnerable operation (unauthorized code execution path).
If you're affected
- Full device takeover
- Malware installation
- Business downtime
- Data theft risk
Exploitation
Where each signal puts this CVE on the scale from published to confirmed exploited.
- CISA KEV
Not in the catalog. CISA has not confirmed exploitation.
- Public exploits
No public exploit or proof of concept found in the sources we track.
- EPSS
0.4% chance of exploitation activity in the next 30 days, which ranks it in the 27th percentile of scored CVEs.
Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.
Lifecycle
12 events over 8 days, from the signal feeds we watch.
- Patch availablerecord updated
- OpenVAS check addedpatch available, record updated
- Record updatedrecord updated
- Publishedweakness classified, att&ck mapped, record updated, record updated
Affected products
Technical detail
CVSS 3.1 vector
Open in the CVSS calculatorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Scored 7.8 by NVD.
How it is reached
- Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
- Attack Complexity LowNo special conditions — the attack can be reliably reproduced
- Privileges Required NoneNo authentication required — anyone can exploit this
- User Interaction RequiredA user must click a link, open a file, or perform some action
Scope
- Scope UnchangedImpact is limited to the vulnerable component itself
Impact if exploited
- Confidentiality HighTotal information disclosure — all data in the component is compromised
- Integrity HighTotal loss of integrity — attacker can modify any data in the component
- Availability HighTotal denial of service — the component is completely unavailable
Weaknesses
ATT&CK techniques
Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.
- Privilege EscalationT1068Exploitation for Privilege Escalationhigh confidence
Sources
References in the record
In the news
Watch the software you run.
My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.
We'll flag the next CVE, public exploit or patch for Windows 11 Version 24H2, not every advisory.
A free account adds
- The full version matrix and every affected product
- Exploit links, proofs of concept and Metasploit modules
- Email alerts for the products you watch
- The same data over REST API, MCP and CLI