Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessCraft malicious image (TIFF/BMP/WDP)
-
DeliveryDeliver via phishing email or malicious web link
-
ExploitVictim opens or previews file in Explorer/Office
-
ExecutionWIC heap buffer overflow triggered in process memory
-
ImpactArbitrary shellcode executed as victim user
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 | The victim must cause Windows to render a specially crafted image through the WIC decoding pipeline. This is triggered by: explicitly opening an image file in any WIC-backed viewer (Photos app, Paint, legacy IE/Edge, Office), navigating to the image's parent folder in Windows Explorer with the Preview Pane enabled (hover sufficient in some configurations), or opening an Office document, web page, or email embedding the malicious image. No authentication to the target system, no elevated privileges, and no non-default configuration are required - WIC and Windows Explorer Preview Pane are enabled by default across all affected Windows editions. Exploitation is constrained by UI:R: a social engineering step (phishing email, malicious website, shared folder lure) must induce the target user to interact with the crafted file. On Windows Server Core installations, the desktop shell is absent, narrowing exploitation to application-layer WIC consumers such as IIS image-processing modules or document conversion services. |
| Impact | The CVSS 8.8 with AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H reflects a high-severity, network-reachable RCE gated only by a single user interaction. AC:L signals no special preconditions or race conditions are required beyond inducing the user to render a crafted image. The practical exploitation bar is further lowered by Windows Explorer's Preview Pane, which can render images without an explicit double-click, reducing UI:R to a hover or folder-navigation action. WIC's integration with Office and web-adjacent applications means delivery vectors include email attachments, malicious websites, and network shares. The broad affected range - 19 distinct Windows builds covering desktop and server SKUs from 2012 to 2026 - indicates a widely distributed attack surface. No CISA KEV listing and no confirmed POC at time of analysis provide some short-term risk reduction, but the straightforward trigger mechanism and ubiquitous target population make weaponization likely if unpatched. EPSS data was not provided; exploitation probability cannot be independently quantified. No conflict between the CVSS vector and the description is observed - network delivery of a malicious image file is consistent with AV:N/UI:R. |
| Exploit ScenarioDerived | An attacker crafts a malicious TIFF or BMP image engineered to trigger a heap buffer overflow in the WIC decoder, then delivers it as an email attachment or hosts it on a phishing site. When the victim opens the file or navigates to the containing folder with Windows Explorer's Preview Pane enabled, WIC decodes the image in-process, the overflow corrupts heap metadata, and the attacker achieves arbitrary code execution in the context of the victim's user account. No public exploit code is confirmed at time of analysis, but the well-understood heap overflow primitive in a widely-studied codebase lowers the reverse-engineering barrier for a skilled attacker. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Sep 08, 2026
Heap-based buffer overflow in Windows Imaging Component (WIC) enables remote unauthenticated attackers to execute arbitrary code on affected Windows systems when a user opens or previews a specially crafted image file. Affected platforms span Windows 10/11 desktop editions and Windows Server 2012 through 2025, covering a core OS image-processing library consumed by Explorer, Office, and countless third-party applications. No public exploit identified at time of analysis, but the unauthenticated network-reachable vector with a low-friction user-interaction trigger makes this a high patch-priority item given the enormous install base.
RemediationAI
Apply the Microsoft-released patches via Windows Update or WSUS referencing the MSRC advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-73013. Target fix builds by platform: Windows 11 25H2 → 10.0.26200.9445; Windows 11 26H1 → 10.0.28000.2954; Windows 11 24H2 → 10.0.26100.9445; Windows 11 23H2 → 10.0.22631.7582; Windows 10 22H2 → 10.0.19045.7725; Windows 10 21H2 → 10.0.19044.7725; Windows 10 1809 → 10.0.17763.9245; Windows 10 1607 → 10.0.14393.9512; Windows Server 2025 → 10.0.26100.33438; Windows Server 2022 → 10.0.20348.5622; Windows Server 2019 → 10.0.17763.9245; Windows Server 2016 → 10.0.14393.9512; Windows Server 2012 R2 → 6.3.9600.23397; Windows Server 2012 → 6.2.9200.26349. As a temporary compensating control, disable the Preview Pane in Windows Explorer (View → Preview Pane off) to prevent automatic WIC invocation on file hover - note this degrades usability. Email gateways can block or quarantine common image container formats (TIFF, WDP, ICO, BMP) as an additional layer, though this is operationally disruptive and bypassed by embedded images in Office documents. Prioritize server-side systems running web or document services that call WIC programmatically.
Affected VersionsENISA
Affected Packages
Source: OSV (Open Source Vulnerabilities)
Affects your stack
Affects 19 packages in euvd
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
Windows Imaging Component (WIC) is a built-in Windows platform framework that provides a standardized API for decoding and encoding image formats including BMP, JPEG, PNG, TIFF, GIF, ICO, HD Photo/WDP, and RAW. It is invoked automatically by Windows Shell (Explorer thumbnail/preview pane), legacy Internet Explorer/Edge, Microsoft Office, Paint, and any third-party application using the WIC COM API. The root cause is CWE-122 (Heap-based Buffer Overflow): a crafted image file triggers a write past the end of a heap-allocated buffer during codec-level decoding. In this class of vulnerability, adjacent heap metadata or function pointers are typically overwritten, allowing the attacker to redirect execution. Because WIC is a shared COM in-process component, exploitation targets the address space of the calling process (e.g., Explorer or an Office application), granting code execution at the victim user's privilege level. Affected builds span from Windows 6.2.9200.0 (Server 2012) through 10.0.28000.0 (Windows 11 26H1) as confirmed by EUVD CPE data, indicating a systemic parser-layer flaw rather than a narrow version-specific regression.
Know when Windows 10 1607 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
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Network-delivered malicious image requires only user interaction to trigger WIC heap overflow; no authentication or special configuration needed; full C/I/A impact in process context.
Primary rating from Vendor (microsoft).
CVSS VectorVendor: microsoft
Lifecycle Timeline
2DescriptionCVE.org
Heap-based buffer overflow in Windows Imaging Component allows an unauthorized attacker to execute code over a network.
Executive ViewAI
Windows Imaging Component affects Windows 10/11, Windows Server 2012-2025, and Office installations across potentially hundreds of millions of endpoints. The vulnerability enables arbitrary code execution when users open specially crafted images-a low-friction attack vector that poses significant organizational risk. Although no public exploit has currently been identified, a patch is available and requires urgent deployment to prevent system compromise.
Apply vendor patch.
Threat Intelligence Overview
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.
What every action level means
SSVC AssessmentENISA
Priority Score
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.
More in Windows 10 1607
View allWindows MSHTML component contains a remote code execution vulnerability that allows attackers to craft malicious ActiveX
<p>A remote code execution vulnerability exists when the Windows Print Spooler service improperly performs privileged fi
Windows MSDT (Microsoft Support Diagnostic Tool) allows remote code execution when called via the ms-msdt URL protocol f
The SMBv1 server in Microsoft Windows Vista SP2; Windows Server 2008 SP2 and R2 SP1; Windows 7 SP1; Windows 8.1; Windows
The Windows VBScript engine contains a remote code execution vulnerability in object handling that allows full system co
Windows Print Spooler Remote Code Execution Vulnerability. Rated high severity (CVSS 7.8), this vulnerability is no auth
The Win32k kernel-mode driver in Windows Vista through Windows Server 2016 allows local privilege escalation, exploited
Windows Search Remote Code Execution Vulnerability. Rated high severity (CVSS 7.5), this vulnerability is remotely explo
Denial of service against HTTP/2 server implementations allows remote unauthenticated attackers to exhaust server resour
Windows Kernel contains a TOCTOU race condition vulnerability allowing local privilege escalation, exploited by the OilR
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
An elevation of privilege vulnerability exists in Windows when the Win32k component fails to properly handle objects in
EUVD-2026-73777
GHSA-f4j7-2j86-4r93
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB