CVE Tools

CVE-2026-50387

Windows GDI Elevation of Privilege Vulnerability

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

Published Updated Sources: CVE.org, NVD

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
  1. Check whether you run Microsoft Windows (Windows 10/11 and Windows Server 2012/2012 R2/2016/2019) with updates applied.
  2. For Microsoft Office 365 for Mac and Microsoft Office LTSC for Mac 2021/2024, confirm you are on 16.111.26071215.
  3. For Microsoft Office for Android, confirm you are on 16.0.20228.20042.
  4. For Windows 10, upgrade to one of the fixed builds: 10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, or 10.0.19045.7548 (use the one that matches your Windows 10 version).
  5. For Windows 11, upgrade to one of the fixed builds: 10.0.26100.8875, 10.0.26200.8875, or 10.0.28000.2269 (use the one that matches your Windows 11 version).
  6. For Windows Server 2012, upgrade to 6.2.9200.26226.
  7. Apply the vendor update from the Microsoft Security Response Center guidance for CVE-2026-50387, then re-check that the affected versions are fully updated.

What it is

From the CVE record

Stack-based buffer overflow in Windows GDI allows an authorized attacker to elevate privileges locally.

In plain language

Written by AI from the record

CVE-2026-50387 is a Windows/Office-related flaw that can let a local attacker run code with higher privileges; you should worry if someone with local access can reach your devices, because it can lead to full system control.

CVE-2026-50387 is a stack-based buffer overflow in Windows GDI that can allow an authenticated/authorized local attacker to elevate privileges and execute arbitrary code with elevated rights on vulnerable Windows systems and affected Office clients.

If you're affected

  • Full device takeover
  • Compromised business email/documents
  • System instability or outage
  • Malware installation with admin rights

Exploitation

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

EPSS24th
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.3% chance of exploitation activity in the next 30 days, which ranks it in the 24th percentile of scored CVEs.

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

Lifecycle

12 events over 27 days, from the signal feeds we watch.

  1. Patch availablerecord updated
  2. Patch availablerecord updated
  3. Record updated
  4. Record updated
  5. Publishedweakness classified, att&ck mapped, record updated, record updated
  6. OpenVAS check added

Affected products

Technical detail

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

Scored 7.8 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 LowRequires basic user-level privileges
  • 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

Weaknesses

ATT&CK techniques

Mapped from the weaknesses above (CWE to ATT&CK), not observed in attacks.

Sources

Watch the software you run.

My Stack ranks new CVEs for your products by real-world exploitation, so the next serious one reaches you without reading every advisory.

We'll flag the next CVE, public exploit or patch for 365 Copilot, not every advisory.

We use analytics cookies to see which pages and articles actually help people. Decline and none of them run — the site works the same. What we store