dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-25181

HIGH · 7.5 CVSS v3.1 Published 2026-03-10
Fix available
A fix is available. Upgrade to 10.0.14393.8957 / 10.0.17763.8511 or later.
See remediation →
84/100
Remediation priority · High
Remotely reachable No privileges Zero-click

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
Out-of-bounds read in Windows GDI+ allows an unauthorized attacker to disclose information over a network.

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 · moderate confidence

An out-of-bounds read vulnerability exists in Windows GDI+ (Graphics Device Interface Plus) that allows an unauthenticated remote attacker to read memory contents beyond allocated buffers, potentially exposing sensitive information. The network attack vector and CVSS 7.5 indicate significant risk for systems processing untrusted graphical content.

MitigationApply Microsoft security patches for GDI+ when available; until then, restrict network exposure of affected Windows systems and disable unnecessary graphical file processing services where possible.

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.8957
Windows 10 1809Operating system
Affected:< 10.0.17763.8511
Windows 10 21h2Operating system
Affected:< 10.0.19044.7058
Windows 10 22h2Operating system
Affected:< 10.0.19045.7058
Windows 11 23h2Operating system
Affected:< 10.0.22631.6783
Windows 11 24h2Operating system
Affected:< 10.0.26100.7979
Windows 11 25h2Operating system
Affected:< 10.0.26200.7979
Windows 11 26h1Operating system
Affected:< 10.0.28000.1719

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
None
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

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. Check Windows version and build number
    Run 'winver' or check System Information (msinfo32) to find the exact Windows version and build number displayed on the first screen, or run 'reg query "HKLM\SOFTWARE\Microsoft\Windows NT\CurrentVersion" /v CurrentBuild' in Command Prompt
    Affected if The installed build number is lower than any of these thresholds: 14393.8957 (Win10 1607), 17763.8511 (Win10 1809), 19044.7058 (Win10 21h2), 19045.7058 (Win10 22h2), 22631.6783 (Win11 23h2), 26100.7979 (Win11 24h2), 26200.7979 (Win11 25h2), or 28000.1719 (Win11 26h1)
  2. Confirm GDI+ component presence
    Verify that gdiplus.dll exists in the system by checking C:\Windows\System32\gdiplus.dll (or use 'dir C:\Windows\System32\gdiplus.dll' in Command Prompt)
    Affected if The file exists, which is standard on all affected Windows installations - GDI+ is a core graphics component
  3. Identify graphical content processing exposure
    Review running services and applications that accept or process graphical image files from network sources, such as web servers, email gateways, document converters, or imaging services. Check with 'netstat -an' for listening services on ports that accept external input
    Affected if The system runs services that process untrusted graphical content from network sources (e.g., web servers handling image uploads, email servers processing attachments, or any application that parses image files from external sources)

You are affected if your Windows build number is lower than the threshold for your specific Windows version and your system processes graphical content from network sources.

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.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.8957 / 10.0.17763.8511 / 10.0.19044.7058 or later
Fixed in 10.0.14393.895710.0.17763.851110.0.19044.7058
Interim mitigation

Apply Microsoft security patches for GDI+ when available; until then, restrict network exposure of affected Windows systems and disable unnecessary graphical file processing services where possible.

Recommended fix High confidence

Apply the relevant Windows security update containing the CVE-2026-25181 fix for your specific Windows version (e.g., Windows 10 1607: 10.0.14393.8957 or later, Windows 11 23h2: 10.0.22631.6783 or later)

  1. Open Windows Settings by pressing Win+I
  2. Navigate to Update & Security > Windows Update
  3. Click Check for updates to scan for available security updates
  4. Locate and install the security update containing the fix for CVE-2026-25181 (typically part of a monthly cumulative update)
  5. Restart the computer if prompted to complete the installation
  6. Verify the installed build number matches or exceeds the fixed version for your Windows release
Caveat Standard Windows security update with minimal risk; ensure regular backups before applying updates in enterprise environments

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Windows 10 1607 Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA2.0 h
20.0 hours of engineering $3,500
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-25181 — 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-25181 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