Skip to main content

Windows Image Acquisition EUVDEUVD-2026-99913

| CVE-2026-83523 HIGH
Heap-based Buffer Overflow (CWE-122)
2026-10-13 secure@microsoft.com GHSA-r544-2pm4-5734
8.8
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Deliver crafted image to victim
  2. Exploit
    Trigger heap overflow in Windows Image Acquisition
  3. Execution
    Corrupt heap and hijack execution
  4. 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 the victim to open or process an attacker-crafted image through the Windows Image Acquisition (WIA) component (UI:R - user interaction is mandatory), so this is not a zero-click flaw. No authentication is required of the attacker (PR:N) and no special non-default configuration is indicated in the description. The user-interaction requirement is the primary limiting factor and is reflected in CISA's SSVC 'Automatable: no' rating, meaning reliable mass/automated exploitation is unlikely; realistic risk centers on social-engineering delivery (malicious attachments/downloads) to a user on an unpatched Windows 11 (24H2/25H2/26H1/26H2) or Windows Server 2025 build below the fixed version.

Impact

This is a genuinely high-priority patch-now issue, though not an emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H, 8.8) indicates a network-reachable, low-complexity, unauthenticated flaw yielding full confidentiality/integrity/availability impact (code execution), with the only brake being required user interaction (UI:R). CISA's SSVC framework tempers the urgency: Exploitation is rated 'none' (no observed or public exploitation) and Automatable is 'no' (the UI:R requirement prevents reliable worming/mass-automation), while Technical Impact is 'total' - consistent with heap-overflow code execution. These signals are internally coherent: high raw severity driven by impact, but the real-world exploitation path depends on luring a user to process a malicious image, which lowers scalability. No EPSS score, KEV listing, or POC was provided in the input; absence of these is not evidence of safety but does mean there is currently no confirmed active exploitation or public exploit to drive opportunistic attacks. Net assessment: a serious, broadly-applicable Windows code-execution bug worth prioritizing in normal patch cycles, but not showing signs of in-the-wild exploitation at time of analysis.

Exploit ScenarioDerived

An attacker crafts a malicious image file and delivers it to a victim (via email attachment, web download, or a networked scanner/camera path handled by Windows Image Acquisition); when the user opens or lets Windows process the image, the heap-based buffer overflow triggers and executes attacker-controlled code in the user's context. The attack is network-deliverable and low-complexity but requires that user interaction (UI:R) to succeed. No public exploit code was identified in the provided data.

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Heap-based buffer overflow in Windows Image Acquisition (WIA) allows an unauthenticated remote attacker to execute arbitrary code on Windows 11 (24H2, 25H2, 26H1, 26H2) and Windows Server 2025 systems, but only after the victim opens or processes a specially crafted image through the WIA component (UI:R), so exploitation requires user interaction rather than being zero-click. CVSS 3.1 scores this 8.8 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H / CWE-122), CISA's SSVC rates it Automatable: no with total technical impact, and no public exploit has been identified at time of analysis. Vendor patches are available from Microsoft, making this a high-priority patch-now issue for unpatched builds rather than an emergency driven by active exploitation.

RemediationAI

Apply the vendor security update from Microsoft; patch status is 'Patch available per vendor advisory' (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83523), and the build levels at or above which the EUVD ranges indicate affected systems are fixed are 10.0.28000.3231 (Windows 11 26H1), 10.0.26300.9711 (26H2), 10.0.26200.9711 (25H2), 10.0.26100.9711 (24H2), and 10.0.26100.33650 (Windows Server 2025, including Server Core). Prioritize internet-facing and user-workstation fleets, and expect a reboot to complete installation. Because exploitation hinges on user interaction with a malicious image, interim compensating controls should focus on delivery paths: enforce email attachment filtering and block or quarantine untrusted image formats and archive-contained images at the gateway, verify that Mark-of-the-Web/Attachment Manager protections and macro-and-preview hardening are enforced so users do not silently render untrusted images, and restrict or monitor SMB/remote share paths that could host crafted image files. Where imaging is not needed - typically Windows Server 2025 Server Core and hardened server builds - consider disabling the Windows Image Acquisition service (stisvc) and unregistering/blocking unused WIA components; the trade-off is that scanner, camera, and some document-capture workflows, including WIA-dependent third-party applications, will stop functioning, so validate before removing the service in production. Patch deployment remains the only complete fix; the mitigations above reduce exposure but do not eliminate the heap overflow. Note there is no public exploit identified at time of analysis and CISA SSVC rates the flaw as not automatable, so scheduling the update within a normal critical-patch window is appropriate for most organizations.

Affected VersionsENISA

Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2025 (Server Core installation) 10.0.26100.0 <10.0.26100.33650

Affected Packages

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_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 6 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 Image Acquisition (WIA) is Microsoft's COM-based imaging stack that brokers communication between applications and image sources such as scanners, cameras, and still-image files, and it relies on Windows image codecs to parse the image data it passes along. The flaw is a heap-based buffer overflow (CWE-122): a bounds or length check on a heap-allocated buffer is insufficient when handling attacker-crafted image content, permitting out-of-bounds writes that corrupt adjacent heap data. Because CVSS scope is unchanged (S:U), the resulting code execution is constrained to the security authority of the WIA-related component and the process that invokes it, but with high confidentiality, integrity, and availability impact that still represents full compromise of that context in most realistic deployments. The network vector (AV:N) reflects that the malicious image can be delivered over a network - via email attachment, download, or a shared/remote file path - even though a user must then open or process it (UI:R). No CPE strings were provided in the source data; affected platform identification comes from the EUVD build ranges covering Windows 11 24H2/25H2/26H1/26H2 and Windows Server 2025, both full and Server Core installations.

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 8.8 HIGH
AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
vuln.today AI 8.8 HIGH

Image is delivered over the network (AV:N) and parsed without attacker auth (PR:N), but needs the user to open it (UI:R); heap overflow enables code execution with full C/I/A impact.

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
Required
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:19 cve.org
HIGH 8.8

DescriptionCVE.org

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

Executive ViewAI

Why It Matters

A high-severity memory corruption flaw in the Windows Image Acquisition (WIA) component affects the organization's Windows 11 (24H2, 25H2, 26H1, 26H2) and Windows Server 2025 estates, where successful exploitation could give an attacker full control of an affected endpoint. The risk is meaningful because the flaw is remotely reachable and unauthenticated, though an attacker must first persuade a user to open or process a crafted image file, so it is a targeted-phishing-style threat rather than a self-propagating one. No public exploit code or active exploitation has been identified, so leadership should treat this as a scheduled, high-priority patch-now remediation rather than an incident-response emergency.

Business Impact: High
Compensating Controls

Apply vendor patch. Where patching cannot be completed immediately, disable or restrict the Windows Image Acquisition service (stisvc) on systems that do not require it, and filter untrusted image attachments at email and web gateways.

Threat Intelligence Overview

EPSS Score
0.8%
Top 43% exploitable
Prevalence
Ubiquitous
Windows client and server OS, present in a huge fraction of environments
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
4 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.8%
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
Open
Automatable
No
Human Impact
High
Technical Impact
Total

Priority Score

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

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