PoC Monitor
← All CVEs
CVE-2026-32202published 14 Apr 2026 16:57 UTCData: JSON · API

Microsoft Windows 10

Windows Shell Spoofing Vulnerability

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

First public PoC 44 daysafter publication · 29 May 2026 · Exploit-DB
Public PoCs43 on GitHub · 1 Exploit-DB, Metasploit or nuclei
CVSS4.3medium · scored by CNA · CWE-693
CISA KEV 28 Apr 202614 days after publication

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

Microsoft Windows 10 Version 1607
  • >= 10.0.14393.0, < 10.0.14393.9339

Fixed in 10.0.14393.9339

Microsoft Windows 10 Version 1809
  • >= 10.0.17763.0, < 10.0.17763.9020

Fixed in 10.0.17763.9020

Microsoft Windows 10 Version 21H2
  • >= 10.0.19044.0, < 10.0.19044.7548

Fixed in 10.0.19044.7548

Microsoft Windows 10 Version 22H2
  • >= 10.0.19045.0, < 10.0.19045.7548

Fixed in 10.0.19045.7548

Microsoft Windows 11 version 23H2
  • >= 10.0.22631.0, < 10.0.22631.7376

Fixed in 10.0.22631.7376

Microsoft Windows 11 Version 23H2
  • >= 10.0.22631.0, < 10.0.22631.7376

Fixed in 10.0.22631.7376

Microsoft Windows 11 Version 24H2
  • >= 10.0.26100.0, < 10.0.26100.8875

Fixed in 10.0.26100.8875

Microsoft Windows 11 Version 25H2
  • >= 10.0.26200.0, < 10.0.26200.8875

Fixed in 10.0.26200.8875

Microsoft Windows 11 version 26H1
  • >= 10.0.28000.0, < 10.0.28000.2525

Fixed in 10.0.28000.2525

Microsoft Windows Server 2012
  • >= 6.2.9200.0, < 6.2.9200.26226

Fixed in 6.2.9200.26226

Microsoft Windows Server 2012 (Server Core installation)
  • >= 6.2.9200.0, < 6.2.9200.26226

Fixed in 6.2.9200.26226

Microsoft Windows Server 2012 R2
  • >= 6.3.9600.0, < 6.3.9600.23291

Fixed in 6.3.9600.23291

Microsoft Windows Server 2012 R2 (Server Core installation)
  • >= 6.3.9600.0, < 6.3.9600.23291

Fixed in 6.3.9600.23291

Microsoft Windows Server 2016
  • >= 10.0.14393.0, < 10.0.14393.9339

Fixed in 10.0.14393.9339

Microsoft Windows Server 2016 (Server Core installation)
  • >= 10.0.14393.0, < 10.0.14393.9339

Fixed in 10.0.14393.9339

Microsoft Windows Server 2019
  • >= 10.0.17763.0, < 10.0.17763.9020

Fixed in 10.0.17763.9020

Microsoft Windows Server 2019 (Server Core installation)
  • >= 10.0.17763.0, < 10.0.17763.9020

Fixed in 10.0.17763.9020

Microsoft Windows Server 2022
  • >= 10.0.20348.0, < 10.0.20348.5386

Fixed in 10.0.20348.5386

Microsoft Windows Server 2025
  • >= 10.0.26100.0, < 10.0.26100.33158

Fixed in 10.0.26100.33158

Microsoft Windows Server 2025 (Server Core installation)
  • >= 10.0.26100.0, < 10.0.26100.33158

Fixed in 10.0.26100.33158

Mitigation

Upgrade Windows 10 Version 1607 to 10.0.14393.9339 or later.

Upgrade Windows 10 Version 1809 to 10.0.17763.9020 or later.

Upgrade Windows 10 Version 21H2 to 10.0.19044.7548 or later.

Upgrade Windows 10 Version 22H2 to 10.0.19045.7548 or later.

Upgrade Windows 11 version 23H2 to 10.0.22631.7376 or later.

Upgrade Windows 11 Version 23H2 to 10.0.22631.7376 or later.

Upgrade Windows 11 Version 24H2 to 10.0.26100.8875 or later.

Upgrade Windows 11 Version 25H2 to 10.0.26200.8875 or later.

Upgrade Windows 11 version 26H1 to 10.0.28000.2525 or later.

Upgrade Windows Server 2012 to 6.2.9200.26226 or later.

Upgrade Windows Server 2012 (Server Core installation) to 6.2.9200.26226 or later.

Upgrade Windows Server 2012 R2 to 6.3.9600.23291 or later.

Upgrade Windows Server 2012 R2 (Server Core installation) to 6.3.9600.23291 or later.

Upgrade Windows Server 2016 to 10.0.14393.9339 or later.

Upgrade Windows Server 2016 (Server Core installation) to 10.0.14393.9339 or later.

Upgrade Windows Server 2019 to 10.0.17763.9020 or later.

Upgrade Windows Server 2019 (Server Core installation) to 10.0.17763.9020 or later.

Upgrade Windows Server 2022 to 10.0.20348.5386 or later.

Upgrade Windows Server 2025 to 10.0.26100.33158 or later.

Upgrade Windows Server 2025 (Server Core installation) to 10.0.26100.33158 or later.

References

Timeline

Days relative to CVE publication
t=0+7+14+21+28+35+42CVE published14 Apr 2026 · t = 0Added to CISA KEV28 Apr 2026 · t+14dFirst public PoC29 May 2026 · t+44d

First public PoC 44 days after publication; added to CISA KEV 14 days after publication. First PoC: Microsoft - NTLMv2 Hash Capture (Exploit-DB, 29 May 2026).

PoC repositories

Found on GitHub.

3 PoCs · 1 informational · 1 suspicious or fake

PoCs 3
RepositoryCreatedStarsAssessment
asdrf5gh67j8ki/CVE-2026-32202 21 Jun 2026 +68 d 0 PoC via PoC Index
f0xox/CVE-2026-32202 21 Jun 2026 +68 d 0 PoC via PoC Index
foxfxfxx/CVE-2026-32202 21 Jun 2026 +68 d 0 PoC via PoC Index
Informational 1
RepositoryCreatedStarsAssessment
solarlynxsqueeze/CVE-2026-32202 30 Apr 2026 +16 d 0 Informational · write-up
Flags · score 15
  • owner account created less than 30 days before the repo

Below the suspicion threshold (50); does not change the assessment.

Suspicious or fake 1
RepositoryCreatedStarsAssessment
virus-or-not/CVE-2026-32202 30 Apr 2026 +16 d 8 Fake

Only PoCs count toward the first-PoC date and the characteristics below. Do not run PoC code from unknown sources.

Other public exploits

Exploit-DB, Metasploit and nuclei count as public PoCs. Exploit-tagged references from the CVE record and NVD are links only. None of these are analysed by us.
SourceTitlePublishedFound by us
Exploit-DBMicrosoft - NTLMv2 Hash Capture29 May 202614 Nov 2026