dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-50380

CRITICAL · 9.6 CVSS v3.1 Published 2026-07-14
Fix available
A fix is available. Upgrade to 10.0.14393.9339 / 10.0.17763.9020 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges 5 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Heap-based buffer overflow in Windows GDI+ allows an unauthorized attacker to execute code over a network.

In the news

Third-party coverage
Trending covered by 1 outlet this week · latest 1mo ago

Surfaced from public web coverage — external links open in a new tab.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

Heap-based buffer overflow vulnerability in Windows GDI+ (Graphics Device Interface Plus) enables an unauthenticated attacker to achieve remote code execution over a network. The flaw exists in how GDI+ processes certain graphical data, allowing memory corruption that can be exploited to inject and execute arbitrary code.

MitigationApply Microsoft security updates for Windows GDI+ when available; until then, restrict network exposure of affected systems and monitor for indicators of compromise.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Windows 10 1607Operating system
Affected:< 10.0.14393.9339
Windows 10 1809Operating system
Affected:< 10.0.17763.9020
Windows 10 21h2Operating system
Affected:< 10.0.19044.7548
Windows 10 22h2Operating system
Affected:< 10.0.19045.7548
Windows 11 24h2Operating system
Affected:< 10.0.26100.8875
Windows 11 25h2Operating system
Affected:< 10.0.26200.8875
Windows 11 26h1Operating system
Affected:< 10.0.28000.2269< 10.0.28000.2525
Windows Server 2012Operating system
Affected:all versions= r2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify Windows version and build number
    Run 'winver' from command prompt or check System Properties, or run 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to get the exact build number
    Affected if The displayed build number falls below any of the following thresholds: 10.0.14393.9339 (Windows 10 1607), 10.0.17763.9020 (Windows 10 1809), 10.0.19044.7548 (Windows 10 21h2), 10.0.19045.7548 (Windows 10 22h2), 10.0.26100.8875 (Windows 11 24h2), 10.0.26200.8875 (Windows 11 25h2), or 10.0.28000.2269
  2. Confirm Windows Server 2012 or Server 2012 R2
    Run 'systeminfo | findstr /B /C:"OS Name"' to check if the system is Windows Server 2012 or Server 2012 R2
    Affected if The system is any version of Windows Server 2012 or Server 2012 R2 (all versions are affected)
  3. Verify GDI+ component exists
    Check if gdiplus.dll exists in the system: run 'dir C:\Windows\System32\gdiplus.dll' or 'powershell Get-Item C:\Windows\System32\gdiplus.dll'
    Affected if The file exists and the Windows version falls within the affected ranges from step 1 or 2
  4. Confirm GDI+ is accessible to applications
    Check if gdiplus.dll is loadable by attempting to load it or by reviewing which applications use graphical rendering (image viewers, Office applications, browsers). This can be observed via 'tasklist /m | findstr gdiplus' or by monitoring process activity.
    Affected if GDI+ is loaded or available to applications and the Windows version is in the affected list

You are affected if your Windows version is below any of the specified build thresholds for your Windows release, or if you are running any version of Windows Server 2012/2012 R2, and GDI+ (gdiplus.dll) is present and accessible on the system.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to 10.0.14393.9339 / 10.0.17763.9020 / 10.0.19044.7548 or later
Fixed in 10.0.14393.933910.0.17763.902010.0.19044.7548
Interim mitigation

Apply Microsoft security updates for Windows GDI+ when available; until then, restrict network exposure of affected systems and monitor for indicators of compromise.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-50380 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-50380 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data