CVE-2026-32202: Microsoft Windows Protection Mechanism Failure Vulnerability

Published Apr 14, 2026
·
Updated

Microsoft Windows Shell contains a protection mechanism failure vulnerability that allows an unauthorized attacker to perform spoofing over a network.

Other sources

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

NVD

Affected Software

57 affected componentsFixes available
Microsoft Windows
Microsoft Windows 10 1607<10.0.14393.9060
Microsoft Windows 10 1607<10.0.14393.9060
Microsoft Windows 10 1809<10.0.17763.8644
Microsoft Windows 10 1809<10.0.17763.8644
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 21h2<10.0.19044.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 10 22h2<10.0.19045.7184
Microsoft Windows 11 23h2<10.0.22631.6936
Microsoft Windows 11 23h2<10.0.22631.6936
Microsoft Windows 11 24h2<10.0.26100.8246
Microsoft Windows 11 24h2<10.0.26100.8246
Microsoft Windows 11 25h2<10.0.26200.8246
Microsoft Windows 11 25h2<10.0.26200.8246
Microsoft Windows 11 26h1<10.0.28000.1836
Microsoft Windows 11 26h1<10.0.28000.1836
Microsoft Windows Server 2012
Microsoft Windows Server 2012=r2
Microsoft Windows Server 2016<10.0.14393.9060
Microsoft Windows Server 2019<10.0.17763.8644
Microsoft Windows Server 2022<10.0.20348.5020
Microsoft Windows Server 2022 23h2<10.0.25398.2274
Microsoft Windows Server 2025<10.0.26100.32690
Microsoft Windows Server 2022, 23H2 Edition<10.0.25398.2274
10.0.25398.2274
Microsoft Windows 11=26H1
10.0.28000.2525
Microsoft Windows 11=26H1
10.0.28000.2525
Microsoft Windows Server 2012 R2<6.3.9600.23291
6.3.9600.23291
Microsoft Windows Server 2012<6.2.9200.26226
6.2.9200.26226
Microsoft Windows Server 2012<6.2.9200.26226
6.2.9200.26226
Microsoft Windows Server 2012 R2<6.3.9600.23291
6.3.9600.23291
Microsoft Windows Server 2016<10.0.14393.9339
10.0.14393.9339
Microsoft Windows 11=24H2
10.0.26100.8875
Microsoft Windows 11=24H2
10.0.26100.8875
Microsoft Windows Server 2016<10.0.14393.9339
10.0.14393.9339
Microsoft Windows 10=1607
10.0.14393.9339
Microsoft Windows Server 2025<10.0.26100.33158
10.0.26100.33158
Microsoft Windows 10=1607
10.0.14393.9339
Microsoft Windows 11=25H2
10.0.26200.8875
Microsoft Windows 11=23H2
10.0.22631.7376
Microsoft Windows 10=22H2
10.0.19045.7548
Microsoft Windows 11=23H2
10.0.22631.7376
Microsoft Windows 11=25H2
10.0.26200.8875
Microsoft Windows Server 2025<10.0.26100.33158
10.0.26100.33158
Microsoft Windows Server 2022<10.0.20348.5386
10.0.20348.5386
Microsoft Windows 10=22H2
10.0.19045.7548
Microsoft Windows 10=21H2
10.0.19044.7548
Microsoft Windows 10=21H2
10.0.19044.7548
Microsoft Windows 10=22H2
10.0.19045.7548
Microsoft Windows 10=1809
10.0.17763.9020
Microsoft Windows 10=21H2
10.0.19044.7548
Microsoft Windows Server 2019<10.0.17763.9020
10.0.17763.9020
Microsoft Windows 10=1809
10.0.17763.9020
Microsoft Windows Server 2019<10.0.17763.9020
10.0.17763.9020
Microsoft Windows Server 2022<10.0.20348.5386
10.0.20348.5386

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.25398.2274Patch KB5082060
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.28000.2525Patch KB5101649
  3. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.3.9600.23291Patch KB5099444
  4. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 6.2.9200.26226Patch KB5099445
  5. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.14393.9339Patch KB5099535
  6. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.8875Patch KB5101650
  7. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26100.33158Patch KB5099536
  8. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.26200.8875Patch KB5101650
  9. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.22631.7376Patch KB5099414
  10. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19045.7548Patch KB5099539
  11. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.20348.5386Patch KB5099540
  12. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.19044.7548Patch KB5099539
  13. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 10.0.17763.9020Patch KB5099538

Event History

Apr 14, 2026
CVE Published
via Microsoft·02:00 PM
Known Exploited
via Microsoft·02:00 PM
Data Sourced
via Microsoft·02:00 PM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·02:00 PM
Affected Software
Updated
via Microsoft·02:00 PM
Description
CVE Published
via MITRE·04:57 PM
Data Sourced
via MITRE·04:57 PM
DescriptionSeverity
Data Sourced
via NVD·06:17 PM
DescriptionSeverityWeaknessAffected Software
Apr 28, 2026
Data Sourced
via CISA·12:00 AM
RemedyDescriptionAffected Software
Apr 29, 2026
News Published
via BleepingComputer·10:29 AM
News Published
via BleepingComputer·10:30 AM
News Published
via The Register·07:15 PM
News Published
via The Register·07:18 PM
May 29, 2026
Exploit Published
via ExploitDB·12:00 AM
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-32202?

CVE-2026-32202 has been classified as a high-severity vulnerability due to its potential for unauthorized network spoofing.

2

How do I fix CVE-2026-32202?

To fix CVE-2026-32202, you need to apply the security patches provided by Microsoft for the affected Windows products.

3

What are the affected products for CVE-2026-32202?

CVE-2026-32202 affects various Microsoft Windows products, including Windows Server 2012 R2, Windows 10, and Windows 11.

4

Can CVE-2026-32202 be exploited remotely?

Yes, CVE-2026-32202 can be exploited remotely, allowing attackers to perform spoofing attacks over a network.

5

What impact does CVE-2026-32202 have on systems?

The impact of CVE-2026-32202 includes the potential for unauthorized access to system resources and data through spoofing.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203