CVE-2026-32221
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 Microsoft Graphics Component allows an unauthorized attacker to execute code locally.
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 confidenceHeap-based buffer overflow vulnerability in Microsoft Graphics Component enabling local code execution by an unauthorized attacker. This is a memory corruption vulnerability in Windows graphics rendering subsystems that could allow privilege escalation or arbitrary code execution.
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< 10.0.26100.8246< 10.0.26200.8246< 10.0.28000.1836< 10.0.26100.32690CVSS 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
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:L/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.
-
Identify Windows version and buildRun 'systeminfo' or PowerShell: 'Get-ComputerInfo | Select-Object WindowsProductName, OsVersion, OsBuildNumber'Affected if The OS is Windows 11 24h2/25h2/26h1 or Windows Server 2025 with a build number below the fixed versions (26100.8246, 26200.8246, 28000.1836, or 26100.32690 respectively)
-
Get exact build numberRun 'ver' at command prompt or PowerShell: '(Get-ItemProperty 'HKLM:\SOFTWARE\Microsoft\Windows NT\CurrentVersion').CurrentBuild' and '.UBR'Affected if The combined build number (CurrentBuild.UBR) is lower than the fixed version numbers listed above for your Windows edition
-
Confirm graphics component is presentVerify the presence of graphics DLLs: check for gdi32.dll or win32k.sys in %SystemRoot%\System32 using 'dir %SystemRoot%\System32\gdi32.dll'Affected if These core graphics DLLs exist on all Windows desktop and server installations - the component is always present when Windows is installed
You are affected if your system runs Windows 11 24h2, 25h2, 26h1, or Windows Server 2025 with a build number lower than the fixed thresholds (26100.8246, 26200.8246, 28000.1836, or 26100.32690 respectively).
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.26100.824610.0.26100.3269010.0.26200.8246
Apply Microsoft security updates for affected Windows versions once released. Prioritize patching systems with interactive desktop access and user-facing graphics applications.
Windows 11 24h2 build 10.0.26100.8246 or later | Windows 11 25h2 build 10.0.26200.8246 or later | Windows 11 26h1 build 10.0.28000.1836 or later | Windows Server 2025 build 10.0.26100.32690 or later
- Open Settings > Windows Update and check for updates
- Apply the latest cumulative security update for your Windows version
- Restart the system when prompted
- Verify the update by running 'winver' and confirming the build number matches or exceeds the fixed version (26100.8246 for 24h2, 26200.8246 for 25h2, 28000.1836 for 26h1, or 26100.32690 for Server 2025)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $6,176.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-32221 — 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-2026-32221 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