CVE-2026-54122

Windows GDI+ Remote Code Execution Vulnerability

No known exploitation. EPSS puts it in the 27th percentile. A vendor fix is available.

CVSS 3.18.4High EPSS percentile27th0.4% chance in 30 days CISA KEVNot listedNo confirmed exploitation
No public exploit known FixVendor fixNo build named by the sources

Published 2026-07-14Updated 2026-07-16Sources: CVE.org, NVD

NVD CVE.org

What to do

The vendor has published a fix. Version details are below where the sources state them.

Steps

Written by AI from the record

Check which affected Windows edition and version you run (Windows 10/11 or Windows Server 2012/2012 R2/2016/2019/2022/2025).
Verify whether your system has already been updated to one of the fixed build numbers listed by Microsoft for your specific Windows edition.
If you are not at a fixed build, apply the Microsoft update that addresses CVE-2026-54122 from the MSRC update guide.
After updating, confirm the installed build number is now at or above the fixed value for your edition.

Vendor advisory Usually a quick update

Check it yourselfA free OpenVAS check exists for this CVE. Run it against your hosts.Is your organisation exposed?Request an assessment to establish which checks fit your systems.

What it is

From the CVE record

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

In plain language

Written by AI from the record

This is a Windows GDI+ flaw that can let an attacker run arbitrary code on your device without needing a login; if you’re running supported Windows versions, you should act and install the available fixes.

CVE-2026-54122 is a heap-based buffer overflow in Windows GDI+ that enables local arbitrary code execution without authentication or user interaction.

If you're affected

Full device takeover
Malware installation
Data theft from the system
Operational disruption

What is it

Think of Windows GDI+ as a part of Windows that helps handle certain graphics. This bug is like a safety rule that can be bypassed, letting a bad actor force Windows to jump to harmful code. If it’s reachable on a machine, the attacker may be able to take control of that machine and install further malware.

Who is affected

This matters if you run Windows 10, Windows 11, or any of the listed Windows Server versions using the Windows GDI+ component. The flaw does not require a login and does not require the user to click anything, but the findings do not confirm whether it’s reachable in the default configuration. Treat it as a risk when an attacker can run a local attack path on the machine (for example, through an exposed process or a way to get code execution locally), then prioritize patching.

How urgent is it

This is a RED issue because it allows arbitrary code execution on the affected Windows systems, and it requires no authentication or user interaction. Even though the findings don’t document a public exploit or CISA KEV listing, the ability to run code makes timely patching essential.

What to do — in detail

Inventory and identify affected systems
- Record each machine’s exact Windows edition (Windows 10/11 vs. each Server version) and its current build number.
- Focus on machines running the affected Windows products listed for CVE-2026-54122.
Determine whether you’re already fixed
- Compare your installed build number against Microsoft’s fixed build numbers for your edition (below).
- If your build is equal to or higher than the fixed build for your edition, you should be covered.
Patch using Microsoft’s official update
- Use the MSRC update guide for CVE-2026-54122 and install the recommended update for your Windows edition.
- MSRC: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-54122
Edition-specific fixed build targets (install to at least these builds)
- Windows 10 fixed in:
  - 10.0.14393.9339
  - 10.0.17763.9020
  - 10.0.19044.7548
  - 10.0.19045.7548
- Windows 11 fixed in:
  - 10.0.26100.8875
  - 10.0.26200.8875
  - 10.0.28000.2525
- Windows Server 2012 fixed in:
  - 6.2.9200.26226
- Windows Server 2012 R2 fixed in:
  - 6.3.9600.23291
- Windows Server 2016 fixed in:
  - 10.0.14393.9339
- Windows Server 2019 fixed in:
  - 10.0.17763.9020
- Windows Server 2022 fixed in:
  - 10.0.20348.5386
If patching is delayed (temporary measures)
- Reduce exposure to any scenario that could allow an attacker to trigger a local GDI+ code path on the machine.
- Apply your organization’s standard hardening for reducing local attacker opportunities (e.g., least-privilege user accounts and restricting untrusted software). (No specific workaround is provided in the findings; patching is the primary fix.)
Verification after patching
- Re-check the OS build number and confirm it matches/ceeds the fixed build for the edition.
- Confirm updates installed successfully through Windows Update history or your patch management tool.
What to monitor
- Monitor for update compliance (all affected machines on fixed builds).
- Keep an eye on security alerts that indicate attempted exploitation, noting that the findings do not provide confirmed exploitation in the reporting sources.

Technical context

Severity is rated high (CVSS 8.4) based on the ability to execute arbitrary code locally. The weakness is identified as CWE-122 (heap-based buffer overflow) in Windows GDI+, which can lead to memory corruption and arbitrary code execution.

Findings indicate: exploitation status is not confirmed via CISA KEV, no clear dated real-world exploitation report is provided, and no public exploit code is on record. The mechanism is local attack execution (attack vector: local) with no authentication and no user interaction required per the findings. “KEV not listed” means CISA has not yet included this CVE in their known exploited catalog, but the RED verdict reflects the impact and direct code-execution capability on affected Windows versions.

This is a general assessment based on public vulnerability data. It does not account for your specific infrastructure — when in doubt, consult a security specialist.

Exploitation

Where each signal puts this CVE on the scale from published to confirmed exploited.

EPSS27th

CISA KEV

Not in the catalog. CISA has not confirmed exploitation.

Public exploits

No public exploit or proof of concept found in the sources we track.

EPSS

0.4% chance of exploitation activity in the next 30 days, which ranks it in the 27th percentile of scored CVEs.

Exploit Prediction Scoring System, FIRST.org. A probability, not a confirmation.

Lifecycle

9 events over 2 days, from the signal feeds we watch.

2026-07-16OpenVAS check addedpatch available, record updated, record updated
2026-07-14Publishedweakness classified, att&ck mapped, record updated, record updated

Affected products

Microsoftcommercial · US

And 22 more affected products. See all after sign-in

Technical detail

CVSS 3.1 vector

Open in the CVSS calculator

CVSS:3.1/AV:L/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Scored 8.4 by NVD.

How it is reached

Attack Vector LocalRequires local access to the vulnerable system (e.g. local login, malicious file)
Attack Complexity LowNo special conditions — the attack can be reliably reproduced
Privileges Required NoneNo authentication required — anyone can exploit this
User Interaction NoneNo user interaction needed — fully automated exploitation

Scope

Scope UnchangedImpact is limited to the vulnerable component itself

Impact if exploited

Confidentiality HighTotal information disclosure — all data in the component is compromised
Integrity HighTotal loss of integrity — attacker can modify any data in the component
Availability HighTotal denial of service — the component is completely unavailable