CVE-2025-53766
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 · uneditedHeap-based buffer overflow in Windows GDI+ allows an unauthorized attacker to execute code 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 confidenceA heap-based buffer overflow vulnerability in Windows GDI+ (Graphics Device Interface Plus) enables an unauthorized attacker to achieve remote code execution, likely through processing malformed graphics content (e.g., specially crafted image files).
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< 16.0.19127.20000< 16.0.14326.22618< 10.0.10240.21100< 10.0.14393.8330< 10.0.17763.7678< 10.0.19044.6216< 10.0.19045.6216< 10.0.22621.5768CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/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 checksWork through these to decide whether this CVE applies to you.
-
Check Windows 10 versionOpen Command Prompt and run: winver or systeminfo | findstr /B /C:"OS Name" /C:"OS Version". Compare the displayed build number to the affected ranges: 1507 (<10.0.10240.21100), 1607 (<10.0.14393.8330), 1809 (<10.0.17763.7678), 21h2 (<10.0.19044.6216), 22h2 (<10.0.19045.6216)Affected if The displayed Windows 10 build number falls within any of the affected version ranges listed
-
Check Windows 11 22h2 versionOpen Command Prompt and run: winver. Compare the build number (e.g., 22621.xxxx) to the affected threshold of 10.0.22621.5768Affected if Windows 11 build is below 10.0.22621.5768
-
Check Microsoft Office versionOpen any Office application (Word, Excel, PowerPoint), go to File > Account > About [App]. Compare the version number (e.g., 16.0.xxxxx.xxxxx) to the affected threshold of 16.0.14326.22618Affected if Office version is below 16.0.14326.22618 and the system processes untrusted graphics files
-
Check Microsoft 365 Copilot versionOpen any Microsoft 365 application, go to File > Account > About. Compare the version to the affected threshold of 16.0.19127.20000Affected if Microsoft 365 Copilot version is below 16.0.19127.20000 and processes image content
-
Determine exposure to untrusted graphics processingAudit systems for applications or services that automatically process graphics files from untrusted sources (e.g., email attachments, web downloads, file servers). Check if GDI+ image parsing is exposed via email clients, document viewers, or thumbnail generators.Affected if The system or application routinely parses graphics files (JPEG, PNG, BMP, GIF, TIFF) from untrusted or external sources using GDI+
You are affected if your Windows version, Office version, or Microsoft 365 Copilot version falls below the specified thresholds and the system processes untrusted graphics content via GDI+.
Generated from the published advisory. Verify against your own configuration.
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 · scoped10.0.10240.2110010.0.14393.833010.0.17763.7678
Apply Microsoft security updates for Windows GDI+ once released; until then, restrict processing of untrusted graphic files and implement network segmentation to limit exposure.
Windows 10 1507: 10.0.10240.21100 or later | Windows 10 1607: 10.0.14393.8330 or later | Windows 10 1809: 10.0.17763.7678 or later | Windows 10 21h2: 10.0.19044.6216 or later | Windows 10 22h2: 10.0.19045.6216 or later | Windows 11 22h2: 10.0.22621.5768 or later | Office: 16.0.14326.22618 or later |
- Open Windows Update (Settings > Update & Security > Windows Update)
- Click 'Check for updates' to install all available security updates
- For enterprise deployments, deploy the relevant Windows security update (KB) from Microsoft's catalog
- Restart the system after applying updates
- Verify the GDI+ version matches or exceeds the fixed version for your Windows release
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing12.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,616.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-53766 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2025-53766 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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