dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 3 Mar 2026.
Windows 10 1607Operating system · Microsoft

CVE-2026-21510

HIGH · 8.8 CVSS v3.1 Developing Published 2026-02-10
Fix available
A fix is available. Upgrade to 10.0.14393.8868 / 10.0.17763.8389 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Remotely reachable No privileges

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
Protection mechanism failure in Windows Shell allows an unauthorized attacker to bypass a security feature 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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-08-23.

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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
Recommended fix High confidence

Upgrade to Windows 10 1607 build 10.0.14393.8868 or later; Windows 10 1809 build 10.0.17763.8389 or later; Windows 10 21h2 build 10.0.19044.6937 or later; Windows 10 22h2 build 10.0.19045.6937 or later; Windows 11 23h2 build 10.0.22631.6649 or later; Windows 11 24h2 build 10.0.26100.7781 or later; W

  1. Identify the current Windows version by running 'winver' or 'systeminfo' in Command Prompt
  2. Determine if the installed version matches any of the affected versions listed in the CVE advisory
  3. For Windows 10: Navigate to Settings > Update & Security > Windows Update and check for updates, or manually download the applicable KB from the Microsoft Update Catalog
  4. For Windows 11: Navigate to Settings > Windows Update and check for updates
  5. For Windows Server 2012/2012 R2: Since these versions are end-of-life with no fixed version listed, migrate to a supported Windows Server version (e.g., Server 2019, 2022, or 2025)
  6. After applying updates or migrating, verify the version matches or exceeds the fixed release version for your product line
  7. Restart the system as required by the Windows update
Caveat Windows Server 2012 and 2012 R2 are end-of-life with no security updates available; migrating to a newer server version may require application compatibility testing

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,950. Get it fixed fast

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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