Threadlinqs IntelligenceStart free

VulnerabilityCVE-2026-21510Published 2026-02-10

CVE-2026-21510 — Microsoft Windows 10 1607

highCISA KEVPublic exploit2 PoC repos

As of 2026-08-19, CVE-2026-21510 is a HIGH-severity vulnerability in Microsoft Windows 10 1607, CVSS v3.1 8.8, EPSS 24.5% (97.8th percentile). It is listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-02-10), with a US federal remediation deadline of 2026-03-03. Threadlinqs Intelligence links 3 tracked threat campaigns to CVE-2026-21510, most recently “CVE-2026-32202 — Windows Shell Protection Mechanism Failure: NTLM Authentication Coercion via Auto-Parsed LNK Files (CISA KEV)”.

CVSS v3.1
8.8/10High
EPSS
24.5%Higher than 97.8% of scored CVEs
CISA KEV
ListedAdded · due 2026-03-03
Tracked threats
3Campaigns referencing it
Priority
9/10Threadlinqs triage score
Published
Updated 2026-08-19
CVSS v3.1 8.8 (HIGH) · EPSS 24.5% (higher than 97.8% of all scored CVEs) · Priority 9/10 · Published 2026-02-10

Last updated:

What is CVE-2026-21510?

Protection mechanism failure in Windows Shell allows an unauthorized attacker to bypass a security feature over a network.

The record classifies CVE-2026-21510 under weakness class CWE-693. Its CVSS v3 base vector states that the flaw is reachable remotely over the network, needs no prior authentication, needs a user to take an action first, and has high impact on confidentiality, integrity, availability. 23 affected-product entries are recorded, across 1 vendor, listed below. The identifier was first published 260 days ago.

Severity and exploitation probability

CVSS v3.1 base score
8.8 — HIGH
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
EPSS (FIRST)
24.5% probability of exploitation in the next 30 days, higher than 97.8% of all scored CVEs
CISA KEV
Listed since 2026-02-10, federal remediation deadline 2026-03-03
Threadlinqs priority
9/10 — CISA KEV-listed, which Threadlinqs floors at 9
Published
2026-02-10, last modified 2026-08-19

Is CVE-2026-21510 being exploited?

CISA added CVE-2026-21510 to the Known Exploited Vulnerabilities catalog on 2026-02-10, which means the agency holds evidence of exploitation in the wild; US federal civilian agencies had to remediate it by 2026-03-03 under BOD 22-01. Weaponised exploit code for CVE-2026-21510 is publicly available. 2 public proof-of-concept repositories are tracked for this identifier. It currently carries a trending score of 52 in the Threadlinqs vulnerability feed.

Affected products and versions

  • Microsoft: Windows 10 1607, Windows 10 1809, Windows 10 21h2, Windows 10 22h2, Windows 11 23h2, Windows 11 24h2, Windows 11 25h2, Windows Server 2012, Windows Server 2012 r2, Windows Server 2016, Windows Server 2019, Windows Server 2022, Windows Server 2022 23h2, Windows Server 2025

Showing 14 of 23 recorded product entries.

How to fix CVE-2026-21510

Vendor advisory: https://msrc.microsoft.com/update-guide/vulnerability/CVE-2026-21510. Because CVE-2026-21510 is KEV-listed, US federal civilian agencies were required to apply the vendor fix, or stop using the product, by 2026-03-03. Apply the vendor fix referenced above to every affected product listed in this record, then confirm the running version against the vendor advisory.

Threat activity tracking CVE-2026-21510

3 tracked threats in the Threadlinqs corpus reference CVE-2026-21510, either in the campaign’s CVE list or as an indicator on the campaign record.

Sources

Enriched from CVE.org, FIRST EPSS, CISA KEV, GitHub Security Advisories, public proof-of-concept repositories. Last verified by Threadlinqs on .

Vendor advisory and patch

Other references