dbcve.org
Windows 10 1607Operating system · Microsoft

CVE-2026-21246

HIGH · 7.8 CVSS v3.1 Published 2026-02-10
Fix available
A fix is available. Upgrade to 10.0.14393.8868 / 10.0.17763.8389 or later.
See remediation →
80/100
Remediation priority · High
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
Heap-based buffer overflow in Microsoft Graphics Component allows an authorized attacker to elevate privileges 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 confidence

Heap-based buffer overflow vulnerability in Microsoft Graphics Component that allows a locally authorized attacker to corrupt heap memory through the graphics rendering pipeline and elevate privileges to higher integrity levels.

MitigationApply Microsoft security updates for the affected Windows graphics components once released; as an interim control, restrict local untrusted access and monitor for unusual graphics-related process behavior.

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.8868
Windows 10 1809Operating system
Affected:< 10.0.17763.8389
Windows 10 21h2Operating system
Affected:< 10.0.19044.6937
Windows 10 22h2Operating system
Affected:< 10.0.19045.6937
Windows 11 23h2Operating system
Affected:< 10.0.22631.6649
Windows 11 24h2Operating system
Affected:< 10.0.26100.7781
Windows 11 25h2Operating system
Affected:< 10.0.26200.7781
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
Local
Complexity
Low
Privileges
Low
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:L/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 checks

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

  1. Check Windows build version
    Run 'winver' or 'systeminfo | findstr /B /C:"OS Name" /C:"OS Version"' to obtain the exact build number
    Affected if The build version is lower than the threshold for your Windows release (e.g., below 10.0.19045.6937 for Win10 22h2, below 10.0.22631.6649 for Win11 23h2)
  2. Confirm Windows edition and build
    Run 'ver' at command prompt or check 'winver' output for both version and build number (e.g., 10.0.19045.6937)
    Affected if The build falls within the affected ranges: Win10 1607 < 10.0.14393.8868, Win10 1809 < 10.0.17763.8389, Win10 21h2 < 10.0.19044.6937, Win10 22h2 < 10.0.19045.6937, Win11 23h2 < 10.0.22631.6649, Win11 24h2 < 10.0.26100.7781, Win11 25h2 < 10.0.26200.7781, or Server 2012/R2 any version
  3. Verify graphics rendering is enabled
    Check if the device has a graphics adapter and graphics services are running: run 'Get-Service -Name Display' in PowerShell or verify 'dxdiag' can launch
    Affected if Graphics rendering is enabled (this is the default state; the vulnerability requires the graphics pipeline to be present)

You are affected if your Windows build version is lower than the threshold listed for your specific Windows release, and graphics rendering components are active 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.

dbcve · scoped
Upgrade available Upgrade to 10.0.14393.8868 / 10.0.17763.8389 / 10.0.19044.6937 or later
Fixed in 10.0.14393.886810.0.17763.838910.0.19044.6937
Interim mitigation

Apply Microsoft security updates for the affected Windows graphics components once released; as an interim control, restrict local untrusted access and monitor for unusual graphics-related process behavior.

Recommended fix High confidence

Windows 10 1607: 10.0.14393.8868 or later | Windows 10 1809: 10.0.17763.8389 or later | Windows 10 21h2: 10.0.19044.6937 or later | Windows 10 22h2: 10.0.19045.6937 or later | Windows 11 23h2: 10.0.22631.6649 or later | Windows 11 24h2: 10.0.26100.7781 or later | Windows 11 25h2: 10.0.26200.7781 or

  1. Open Windows Settings on the affected system
  2. Navigate to Update & Security > Windows Update
  3. Click 'Check for updates' and install all available updates
  4. Alternatively, manually download and install the specific security update from Microsoft Update Catalog for your Windows version
  5. Verify the installed version matches or exceeds the fixed version for your Windows release
  6. For Windows Server 2012 R2: Since this version is end-of-support, consider upgrading to a supported Windows Server version (e.g., Windows Server 2019 or 2022)
Caveat Windows Server 2012 R2 is end-of-life; no further security patches available - upgrade to newer Server OS required

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

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-21246 — 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-21246 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