CVE-2026-32221: Microsoft Graphics Component heap overflow code execution

CVE-2026-32221 · Severity: high · CVSS 8.4 · Published 2026-04-14

A vulnerability in the Microsoft Graphics Component, which handles visual rendering and image processing in Windows, could allow an attacker to run malicious code on a target system. While the attacker must already have local access to the machine, successful exploitation could lead to a full system compromise, data theft, or permanent damage to the operating system. This affects modern versions of Windows 11 and Windows Server 2025.

Technologies: Microsoft Windows 11, Microsoft Windows Server 2025. Vendors: Microsoft.

Quick answers

Is CVE-2026-32221 exploited in the wild?
No. Junglewise Threat Intelligence has no report of CVE-2026-32221 being exploited in the wild.
How severe is CVE-2026-32221?
High severity, with a CVSS score of 8.4, published 14 April 2026.
Which products and versions are affected?
Microsoft Windows 11 up to (excluding) 10.0.26100.8246; Microsoft Windows Server 2025 up to (excluding) 10.0.26100.32690.
Is there a fix for CVE-2026-32221?
No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
How is CVE-2026-32221 attacked?
It is attacked with local access, in an operating system.
Am I affected by CVE-2026-32221?
Check whether you run Microsoft Windows 11 or Microsoft Windows Server 2025 at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

Technical details

A heap-based buffer overflow (CWE-122) exists within the Microsoft Graphics Component. The vulnerability is triggered when the component improperly handles memory allocation during graphics processing, allowing an attacker to overwrite adjacent memory. Although the attack vector is local (AV:L), it requires no special privileges (PR:N) or user interaction (UI:N). Successful exploitation enables arbitrary code execution with the privileges of the affected process, potentially leading to a full compromise of the host's confidentiality, integrity, and availability. Microsoft has released security updates to address this issue across affected Windows 11 and Windows Server 2025 builds.

Affected products

  • Microsoft Windows 11 Version 24H2 up to (excluding) 10.0.26100.8246
  • Microsoft Windows 11 Version 25H2 up to (excluding) 10.0.26200.8246
  • Microsoft Windows 11 version 26H1 up to (excluding) 10.0.28000.1836
  • Microsoft Windows Server 2025 up to (excluding) 10.0.26100.32690

Timeline

  • 2026-04-14: disclosed: Initial publication by Microsoft
  • 2026-04-14: advisory: MSRC advisory published

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.