CyberSecBulletin
CVE-2026-32202Exploited in the wildNVD status: Analyzed

Microsoft Windows Protection Mechanism Failure

Published Updated By the CyberSecBulletin desk

CVE-2026-32202 is a medium-severity protection mechanism failure vulnerability in Windows 10 Version 1607 from Microsoft, with a CVSS 3.1 base score of 4.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, but only if a user takes part, for example by opening a link or file. The record lists version 10.0.14393.9339 as the first without the flaw, so updating Windows 10 Version 1607 to that release or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on April 28, 2026, which means attacks have been observed in the wild.

Patch now

Attackers are already exploiting this vulnerability, according to CISA.

What to do

  1. Update Windows 10 Version 1607 to 10.0.14393.9339 or a later version.
  2. Update Windows 10 Version 1809 to 10.0.17763.9020 or a later version.
  3. Update Windows 10 Version 21H2 to 10.0.19044.7548 or a later version.
  4. CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
  5. Read the advisory on msrc.microsoft.com for workarounds and exact fixed builds.
  6. Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
  7. Because the attack needs a user to take part, warn users about unexpected links and files related to this product until it is patched.

Affected products and versions

VendorProductAffected versionsFixed in
MicrosoftWindows 10 Version 160710.0.14393.0 up to, but not including, 10.0.14393.933910.0.14393.9339
MicrosoftWindows 10 Version 180910.0.17763.0 up to, but not including, 10.0.17763.902010.0.17763.9020
MicrosoftWindows 10 Version 21H210.0.19044.0 up to, but not including, 10.0.19044.754810.0.19044.7548
MicrosoftWindows 10 Version 22H210.0.19045.0 up to, but not including, 10.0.19045.754810.0.19045.7548
MicrosoftWindows 11 version 23H210.0.22631.0 up to, but not including, 10.0.22631.737610.0.22631.7376
MicrosoftWindows 11 Version 24H210.0.26100.0 up to, but not including, 10.0.26100.887510.0.26100.8875
MicrosoftWindows 11 Version 25H210.0.26200.0 up to, but not including, 10.0.26200.887510.0.26200.8875
MicrosoftWindows 11 version 26H110.0.28000.0 up to, but not including, 10.0.28000.252510.0.28000.2525
MicrosoftWindows Server 20126.2.9200.0 up to, but not including, 6.2.9200.262266.2.9200.26226
MicrosoftWindows Server 2012 (Server Core installation)6.2.9200.0 up to, but not including, 6.2.9200.262266.2.9200.26226
MicrosoftWindows Server 2012 R26.3.9600.0 up to, but not including, 6.3.9600.232916.3.9600.23291
MicrosoftWindows Server 2012 R2 (Server Core installation)6.3.9600.0 up to, but not including, 6.3.9600.232916.3.9600.23291
MicrosoftWindows Server 201610.0.14393.0 up to, but not including, 10.0.14393.933910.0.14393.9339
MicrosoftWindows Server 2016 (Server Core installation)10.0.14393.0 up to, but not including, 10.0.14393.933910.0.14393.9339
MicrosoftWindows Server 201910.0.17763.0 up to, but not including, 10.0.17763.902010.0.17763.9020
MicrosoftWindows Server 2019 (Server Core installation)10.0.17763.0 up to, but not including, 10.0.17763.902010.0.17763.9020
MicrosoftWindows Server 202210.0.20348.0 up to, but not including, 10.0.20348.538610.0.20348.5386
MicrosoftWindows Server 202510.0.26100.0 up to, but not including, 10.0.26100.3315810.0.26100.33158
MicrosoftWindows Server 2025 (Server Core installation)10.0.26100.0 up to, but not including, 10.0.26100.3315810.0.26100.33158
MicrosoftWindows 10 1607before 10.0.14393.906010.0.14393.9060
MicrosoftWindows 10 1809before 10.0.17763.864410.0.17763.8644
MicrosoftWindows 10 21h2before 10.0.19044.718410.0.19044.7184
MicrosoftWindows 10 22h2before 10.0.19045.718410.0.19045.7184
MicrosoftWindows 11 23h2before 10.0.22631.693610.0.22631.6936
MicrosoftWindows 11 24h2before 10.0.26100.824610.0.26100.8246

Version data comes from the organisation that assigned the CVE; 3 further products are omitted here. Confirm against the vendor advisory before deciding you are unaffected.

How the severity score breaks down

Attack vector
NetworkCan be exploited remotely over a network, including the internet.
Attack complexity
LowNo special conditions are needed; the attack works reliably.
Privileges required
NoneNo account or login is needed.
User interaction
RequiredA user must take an action such as opening a file or link.
Scope
UnchangedImpact stays within the vulnerable component.
Confidentiality
LowSome restricted data can be read.
Integrity
NoneNothing can be modified.
Availability
NoneAvailability is not affected.

Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N. Scored by CNA (microsoft.com).

Official description

Protection mechanism failure in Windows Shell allows an unauthorized attacker to perform spoofing over a network.

Source: the CVE record as published by its numbering authority, via NVD and CVE.org.

The underlying weakness: Protection Mechanism Failure

The product does not use or incorrectly uses a protection mechanism that provides sufficient defense against directed attacks against the product.

More Protection Mechanism Failure vulnerabilities (CWE-693)

Timeline

  1. CVE record published.
  2. CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: partial).
  3. Added to CISA's Known Exploited Vulnerabilities catalogue.
  4. Deadline for US federal agencies to remediate, set by CISA.
  5. Record last changed materially (score, affected products, status or references).

References

Recent Protection Mechanism Failure vulnerabilities

Spotted an error? Tell us.