Skip to main content

Windows GDI CVE-2026-83860

| EUVDEUVD-2026-100018 HIGH
Stack-based Buffer Overflow (CWE-121)
2026-10-13 secure@microsoft.com GHSA-2pxw-73v4-635j
7.5
CVSS 3.1 · Vendor: microsoft
View

Attack ChainAIDerived

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

  1. Access
    Reach GDI over network
  2. Exploit
    Send crafted input
  3. Execution
    Trigger stack buffer overflow
  4. Impact
    Crash service, deny availability

Vulnerability Assessment

Weakness
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Stack 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

No special configuration is named in the description - the flaw is in the Windows GDI (graphics device interface) subsystem, which is present by default across all supported Windows client and server editions, including Server Core installations. Per CVSS AV:N/AC:L/PR:N/UI:N, exploitation requires only network reach to a component that processes the attacker-supplied GDI data, with no authentication and no user interaction. The principal limiting factor is impact scope: the outcome is denial of service (A:H, C:N/I:N) - a crash or unavailability - not code execution or data disclosure. Realistic exposure also depends on whether the vulnerable GDI code path is reachable from the network in a given deployment (e.g., a network-facing service that parses the relevant graphics/font data), which the advisory does not specify.

Impact

Signals are mostly aligned toward a moderate, availability-only concern rather than a top-tier emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:N) describes a network-reachable, low-complexity, unauthenticated vulnerability, but the impact is strictly A:H with C:N/I:N - this is a denial-of-service, not code execution or data exposure, so the 7.5 Base score is driven entirely by availability loss. CISA's SSVC framework corroborates this: Exploitation is 'none' (no observed or public exploitation), Technical Impact is 'partial' (consistent with DoS rather than full compromise), while Automatable is 'yes', meaning the crash could be triggered reliably and at scale if an exploit emerged. There is no CISA KEV listing and no POC indicator in the provided data, so this is not a confirmed in-the-wild threat. No EPSS score was provided, so exploitation-probability cannot be quantified here. Net assessment: a legitimate patch-worthy issue because of broad Windows exposure and unauthenticated network reach, but currently lower real-world urgency than a CVSS 7.5 might suggest, since the worst-case outcome is a service/system crash rather than compromise and no exploitation is observed.

Exploit ScenarioDerived

A remote, unauthenticated attacker sends specially crafted data that reaches the Windows GDI component and overflows a stack-based buffer, causing the affected process or system to crash and become unavailable. Because CVSS is AV:N/AC:L/PR:N/UI:N, no credentials or user interaction are required and the attack is low-complexity. No public exploit code is identified at time of analysis, and SSVC lists exploitation as 'none'.

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

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

Alert me

AnalysisAIv1 – Oct 14, 2026

Denial of service in the Windows Graphics Device Interface (GDI) subsystem allows unauthenticated, remote attackers to trigger a stack-based buffer overflow (CWE-121) and crash affected components, requiring no user interaction. The flaw (CVSS:3.1 7.5, AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H) affects all supported Windows client and server editions, including Server Core installations, but impact is confined to availability - there is no confidentiality or integrity loss, code execution, or privilege escalation described. CISA's SSVC assessment records exploitation as "none" and notes the flaw is automatable; no public exploit code was identified at time of analysis, and a vendor patch is available per the Microsoft advisory.

RemediationAI

Patch available per vendor advisory: apply the Microsoft update for CVE-2026-83860 via the MSRC update guide (https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-83860), which raises affected builds to at least the following thresholds - Windows Server 2012 6.2.9200.26434, Windows Server 2012 R2 6.3.9600.23470, Windows Server 2016 and Windows 10 1607 10.0.14393.9612, Windows Server 2019 and Windows 10 1809 10.0.17763.9376, Windows 10 21H2/22H2 10.0.19044.7807, Windows Server 2022 10.0.20348.5761, Windows Server 2025 10.0.26100.33650, Windows 11 23H2 10.0.22631.7652, Windows 11 24H2 10.0.26100.9711, Windows 11 25H2 10.0.26200.9711, Windows 11 26H2 10.0.26300.9711, and Windows 11 26H1 10.0.28000.3231. Because no patch-free configuration change fully removes the vulnerable GDI code path (GDI is a default Windows component and Server Core still exposes it), compensating controls are limited to reducing reachability: restrict or block network access to services on the affected hosts that parse externally supplied graphics, image, or font data, and segment those hosts from untrusted networks - the trade-off is loss of functionality for any legitimate remote graphics/font-processing workflow, and this is only a partial mitigation since the advisory does not identify which network-facing component is reachable. Additional hardening with minimal functional cost includes enabling Windows Firewall default-deny inbound rules on Server Core and server roles, monitoring for repeated unexpected termination of GDI-dependent processes as a crash-oracle indicator, and prioritizing remediation on internet-facing or multi-tenant hosts where the availability impact (A:H) is most consequential; the SSVC "automatable: yes" rating means attackers can attempt the trigger at scale, so internet-exposed systems should be patched on an expedited schedule even though exploitation has not been observed.

Affected VersionsENISA

Windows Server 2016 (Server Core installation) 10.0.14393.0 <10.0.14393.9612
Windows 10 Version 21H2 10.0.19044.0 <10.0.19044.7807
Windows Server 2012 (Server Core installation) 6.2.9200.0 <6.2.9200.26434
Windows Server 2012 6.2.9200.0 <6.2.9200.26434
Windows 11 Version 24H2 10.0.26100.0 <10.0.26100.9711
Windows Server 2019 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 26H2 10.0.26300.0 <10.0.26300.9711
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 10 Version 1607 10.0.14393.0 <10.0.14393.9612
Windows Server 2012 R2 6.3.9600.0 <6.3.9600.23470
Windows Server 2022 10.0.20348.0 <10.0.20348.5761
Windows Server 2012 R2 (Server Core installation) 6.3.9600.0 <6.3.9600.23470
Windows 10 Version 22H2 10.0.19045.0 <10.0.19044.7807
Windows Server 2016 10.0.14393.0 <10.0.14393.9612
Windows 11 version 26H1 10.0.28000.0 <10.0.28000.3231
Windows Server 2019 (Server Core installation) 10.0.17763.0 <10.0.17763.9376
Windows 11 Version 25H2 10.0.26200.0 <10.0.26200.9711
Windows Server 2025 10.0.26100.0 <10.0.26100.33650
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 CWE-121 (stack-based buffer overflow): input taken from network-reachable processing is written into a fixed-length stack buffer without adequate bounds validation, corrupting the stack and terminating the process. GDI is a core Windows subsystem that handles 2D graphics, font rendering, and device-context operations, and it ships enabled by default across supported client and server builds - including the Server Core installation option, which lacks a full desktop but still includes GDI. Because the CVSS vector is AV:N with PR:N and UI:N, the vulnerable code path is assumed to be reachable over the network by an unauthenticated sender with no victim interaction; in practice, that means a network-facing component that parses attacker-supplied graphics, image, or font data (the advisory does not name the specific reachable service). The assessed scope is unchanged (S:U) and the sole impact is A:H, i.e., crash/unavailability rather than memory-corruption-driven code execution. The CPE data was not supplied; affected instance identification therefore rests on the EUVD build-number ranges listed in the vendor advisory.

Know when the next one hits your stack

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

Network-reachable, low-complexity, unauthenticated with no user interaction per vendor vector; impact is availability-only denial of service, so C:N/I:N/A:H.

3.1 AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H
4.0 AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:N/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
None
Integrity
None
Availability
High

Lifecycle Timeline

2
Patch available
Oct 13, 2026 - 20:20 EUVD
CVE Published
Oct 13, 2026 - 19:20 cve.org
HIGH 7.5

DescriptionCVE.org

Stack-based buffer overflow in Windows GDI allows an unauthorized attacker to deny service over a network.

Executive ViewAI

Why It Matters

An unauthenticated, remotely triggerable denial-of-service flaw in the Microsoft Windows graphics (GDI) subsystem can crash unpatched Windows clients and servers - including Server Core builds - with no user interaction, giving any network-reachable attacker a low-skill way to knock business services offline. Impact is confined to availability: no data theft, tampering, or code execution is described, so the exposure is service interruption and user productivity loss rather than a breach of confidentiality. There is no public exploit identified at time of analysis and a patch is available, so leadership should treat this as a time-bound patching obligation across the entire Windows estate rather than a crisis requiring emergency containment.

Business Impact: High
Compensating Controls

Apply vendor patch.

Threat Intelligence Overview

EPSS Score
1.1%
Top 34% exploitable
Prevalence
Ubiquitous
Core Windows graphics subsystem across all supported client and server editions
Vendor Status
Publicly Disclosed:No
Exploited:No
Latest Software Release:Exploitation Less Likely
Data Quality
5 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 1.1%
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
Yes
Human Impact
High
Technical Impact
Partial

Priority Score

39
Low Medium High Critical
KEV: 0
EPSS: +1
CVSS: +38
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 stack-based buffer overflow occurs when a program writes more data to a buffer located on the stack than it was allocated to hold.

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