Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessDeliver crafted image via web/email
-
DeliveryTarget WIC auto-parses image
-
ExploitTrigger heap buffer overflow in decoder
-
ExecutionCorrupt heap memory layout
-
ImpactExecute arbitrary code in process 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 the target system to parse an attacker-supplied, malformed image through Windows Imaging Component - delivered via web content, email, documents, or shared files. Per the input CVSS (PR:N, UI:N), it is rated as remote and unauthenticated with no required user action, which is plausible where WIC decodes images automatically (e.g., Explorer thumbnail generation or Outlook/preview-pane rendering). Limiting factors: the attacker must still get malicious image data to reach the WIC decoder, so exposure is highest on systems that auto-render untrusted images and lower where previewing is disabled; successful heap-overflow exploitation may also depend on defeating ASLR/heap mitigations present on modern Windows, which can raise practical complexity above the AC:L rating. Only unpatched builds below the fixed versions listed in EUVD are affected. |
| Impact | Signals are strongly aligned toward high priority with one notable tension. The input CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H, score 9.8) describes trivial network-reachable, unauthenticated, no-interaction code execution with total CIA impact, and the CWE-122 heap overflow in Windows Imaging Component (WIC) is consistent with memory-corruption RCE. CISA SSVC reinforces concern: Automatable=yes and Technical Impact=total, which favors near-term exploitation and reliable full compromise. However, SSVC Exploitation is explicitly 'none,' KEV is NOT listed, and no POC is indicated - so this is a severe but not-yet-exploited flaw rather than an active-attack emergency. Treat exploitation status as: no public exploit identified at time of analysis. A key caveat: WIC is an image-parsing codec component, and real-world triggering typically requires the target to process/render an attacker-supplied image (e.g., preview pane, file open, or a web/email-delivered image). Microsoft's UI:N therefore likely reflects automatic preview-pane rendering counting as 'no explicit user action,' but defenders should verify whether genuine zero-interaction exploitation is possible or whether some user action (viewing content) is needed - this materially changes exposure. Net: a real top-tier patch priority for a ubiquitous platform, driven by severity, automatability, and a vendor patch being available, even though no exploitation has yet been observed. |
| Exploit ScenarioDerived | An attacker delivers a maliciously crafted image file to a target - for example embedding it in a web page, email, document, or chat message - so that Windows Imaging Component parses it, often automatically via the Explorer/Outlook preview pane. The malformed image triggers a heap-based buffer overflow (CWE-122) during decoding, corrupting memory to achieve arbitrary code execution in the context of the processing application. No public exploit code has been identified at time of analysis, though CISA SSVC rates the flaw as automatable with total technical impact. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 14, 2026
Heap-based buffer overflow in the Windows Imaging Component (WIC) - Microsoft's image-decoding framework used across Windows 10, Windows 11, and Windows Server 2012 through 2025 - lets remote, unauthenticated attackers execute arbitrary code by getting a malformed image to reach a WIC decoder. Per our independent assessment the attack is network-reachable and needs no credentials (CVSS PR:N), but practical exploitation requires the victim to parse attacker-supplied image data delivered via a web page, email, document, or shared file, and the vendor's own vector rates it UI:N while our assessed vector reflects UI:R given the need to trigger decoding of the crafted image. Heap-overflow exploitation on hardened Windows builds also requires defeating ASLR and heap mitigations, which can raise real-world complexity above the AC:L rating. A vendor patch is available (Microsoft MSRC update guide) and no public exploit code has been identified at time of analysis; CISA SSVC records exploitation as 'none' with total technical impact and 'automatable: yes', so this should be treated as a high-priority patch-now issue even without evidence of active use.
RemediationAI
Apply the vendor-released Microsoft security update for the appropriate build: Windows 10 21H2/22H2 to 10.0.19044.7807 or later, 1607 to 10.0.14393.9612, 1809 to 10.0.17763.9376; Windows 11 23H2 to 10.0.22631.7652, 24H2 to 10.0.26100.9711, 25H2 to 10.0.26200.9711, 26H1 to 10.0.28000.3231, 26H2 to 10.0.26300.9711; Windows Server 2012 to 6.2.9200.26434, 2012 R2 to 6.3.9600.23470, 2016 to 10.0.14393.9612, 2019 to 10.0.17763.9376, 2022 to 10.0.20348.5761, and 2025 to 10.0.26100.33650 - details and download links are in the Microsoft advisory at https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-69886. Where immediate patching is not possible, reduce the attack surface by interrupting delivery of attacker-controlled images to WIC decoders: disable Explorer thumbnail caching and preview-pane rendering through Group Policy ('Turn off caching of thumbnail pictures' and 'Turn off preview pane'), and disable content preview in Outlook ('Show previews of attachments'). These controls trade off usability - users lose thumbnail/preview convenience and must open files deliberately - and they do not protect against applications that independently decode images through WIC (Office, browsers, .NET/WPF imaging, third-party viewers), so they are stopgaps, not substitutes for the update. Blocking inbound untrusted image attachments at the mail/web gateway and restricting access to untrusted content may further narrow delivery vectors, while acknowledging that CISA SSVC marks the flaw as automatable, so patch deployment should be prioritized across the full Windows fleet including Server Core systems.
Affected VersionsENISA
Affected Packages
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 Windows Imaging Component is a COM-based extensible codec framework at the core of Windows image handling: it backs Explorer thumbnail and preview generation, Photo Viewer, the Outlook preview pane, .NET System.Drawing/WPF imaging paths, and many third-party applications and document renderers. Because it parses complex, highly structured binary formats (JPEG, PNG, TIFF, GIF, BMP, HEIF/HEVC, camera RAW, and vendor-installed codecs), WIC is a high-value memory-safety target. CVE-2026-69886 is a CWE-122 heap-based buffer overflow: while decoding a crafted image, a size or length value derived from the file is trusted without adequate bounds validation, so the decoder writes past the end of a heap allocation. That out-of-bounds write corrupts adjacent heap metadata and objects, which an attacker can shape into controlled memory corruption and ultimately code execution in the context of the decoding process - potentially a privileged Windows service or a user application. The affected CPE/version data spans essentially the entire supported (and some legacy) Windows install base, from 6.2.9200 (Windows Server 2012) through 10.0.28000 (Windows 11 26H1), including Server Core installations, which should be patched even though they lack full desktop image-preview surfaces because WIC decoding is used by many server-side and service components.
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
AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H
Network-delivered, unauthenticated heap overflow with total impact (AV:N/PR:N, C/I/A:H); assessed UI:R because WIC decoding is normally driven by the target processing an attacker-supplied image.
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
A critical vulnerability in Microsoft's Windows Imaging Component (WIC) exposes Windows 10, Windows 11, and Windows Server 2012-2025 to remote code execution, putting organizational endpoints and servers at risk. Leadership should care because a successful attack could lead to unauthorized system control, data breaches, or operational disruption across the enterprise. With a vendor patch available and no public exploit identified at time of analysis, this is a manageable but urgent risk that requires immediate remediation.
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.
Unauthenticated remote code execution in SmarterTools SmarterMail lets an attacker upload arbitrary files to any locatio
Windows Win32k fails to properly handle objects in memory, allowing local privilege escalation exploited in the wild in
A privilege escalation vulnerability (CVSS 5.5). Risk factors: actively exploited (KEV-listed), EPSS 94% exploitation pr
Windows Internet Shortcut Files (.url) contain an external control vulnerability (CVE-2025-33053, CVSS 8.8) that enables
Windows SMB contains an improper access control vulnerability (CVE-2025-33073, CVSS 8.8) enabling authenticated attacker
Twonky Server 8.5.2 on Linux and Windows allows unauthenticated access to the admin log file through a web service API b
An unrestricted file upload vulnerability exists in MiniWeb HTTP Server <= Build 300 that allows unauthenticated remote
FreeFloat FTP Server contains multiple critical design flaws that allow unauthenticated remote attackers to upload arbit
Serviio Media Server versions 1.4 through 1.8 on Windows contain an unauthenticated command injection in the /rest/actio
Twonky Server 8.5.2 uses hard-coded cryptographic keys for encrypting the administrator password. Combined with the cred
Mako Server versions 2.5 and 2.6 contain an unauthenticated OS command injection via the tutorial interface at examples/
React Native Metro Development Server binds to external interfaces by default and contains an OS command injection endpo
EUVD-2026-99445
GHSA-prqh-2r68-h4f2
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB