Skip to content
vulnerability

CVE-2026-32202

4.3
Medium
KEV · Exploited in wildEPSS 71%Patch available

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

exploited
Yes, in CISA KEV since 28 Apr 2026fix by 12 May 2026 (CISA deadline for US federal agencies)public exploit code
fix
Patch available see the advisory in the references
likelihood
EPSS 70.9%
Published 14 Apr 2026Analysed here 2 Nov 2026CVSS scored by the publisher (CNA)

do firstApply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

triage
surface unknownruntimeWAF can block: noAV · networkCWE-693· Common Weakness

Can a WAF block it? No. The vulnerability involves a protection mechanism failure in Windows Shell that allows spoofing over a network, but it does not specify HTTP or web-based input. Therefore, the attack is not delivered via HTTP and cannot be filtered by a web application firewall.

Also consider: patch

Based on an AI reading of the CVE description, and no vendor rule found yet. We check Cloudflare, AWS, Google Cloud Armor and Azure; for Akamai, Imperva, Fastly, F5, ask your vendor.

cvss vector
attack vectornetworkattack complexitylowprivileges requirednoneuser interactionrequiredscopeunchangedconfidentialitylowintegritynoneavailabilitynone
CVSS 3.1 · CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
common questions

Is CVE-2026-32202 being exploited?

Yes. CVE-2026-32202 appears in CISA's Known Exploited Vulnerabilities catalog, which means exploitation in the wild has been confirmed and reported. Treat it as active rather than theoretical, and patch it ahead of higher-scoring vulnerabilities that carry no exploitation evidence.

How severe is CVE-2026-32202?

CVE-2026-32202 is rated Medium with a CVSS score of 4.3. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-32202?

Yes. A fix has been recorded for CVE-2026-32202. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-32202 affect?

CVE-2026-32202 affects microsoft:windows_10_1607, microsoft:windows_10_1809, microsoft:windows_10_21h2, microsoft:windows_10_22h2, and 10 further products or versions. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
microsoft:windows_10_1607microsoft:windows_10_1809microsoft:windows_10_21h2microsoft:windows_10_22h2microsoft:windows_11_23h2microsoft:windows_11_24h2microsoft:windows_11_25h2microsoft:windows_11_26h1microsoft:windows_server_2012microsoft:windows_server_2016microsoft:windows_server_2019microsoft:windows_server_2022microsoft:windows_server_2022_23h2microsoft:windows_server_2025
affected versions
Microsoft Windows 10 Version 1607
  • affected>= 10.0.14393.0 and < 10.0.14393.9339
Microsoft Windows 10 Version 1809
  • affected>= 10.0.17763.0 and < 10.0.17763.9020
Microsoft Windows 10 Version 21H2
  • affected>= 10.0.19044.0 and < 10.0.19044.7548
Microsoft Windows 10 Version 22H2
  • affected>= 10.0.19045.0 and < 10.0.19045.7548
Microsoft Windows 11 version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7376
Microsoft Windows 11 Version 23H2
  • affected>= 10.0.22631.0 and < 10.0.22631.7376
Microsoft Windows 11 Version 24H2
  • affected>= 10.0.26100.0 and < 10.0.26100.8875
Microsoft Windows 11 Version 25H2
  • affected>= 10.0.26200.0 and < 10.0.26200.8875
Microsoft Windows 11 version 26H1
  • affected>= 10.0.28000.0 and < 10.0.28000.2525
Microsoft Windows Server 2012
  • affected>= 6.2.9200.0 and < 6.2.9200.26226
Microsoft Windows Server 2012 R2
  • affected>= 6.3.9600.0 and < 6.3.9600.23291
Microsoft Windows Server 2012 R2 (Server Core installation)
  • affected>= 6.3.9600.0 and < 6.3.9600.23291
Microsoft Windows Server 2012 (Server Core installation)
  • affected>= 6.2.9200.0 and < 6.2.9200.26226
Microsoft Windows Server 2016
  • affected>= 10.0.14393.0 and < 10.0.14393.9339
Microsoft Windows Server 2016 (Server Core installation)
  • affected>= 10.0.14393.0 and < 10.0.14393.9339
Microsoft Windows Server 2019
  • affected>= 10.0.17763.0 and < 10.0.17763.9020
Microsoft Windows Server 2019 (Server Core installation)
  • affected>= 10.0.17763.0 and < 10.0.17763.9020
Microsoft Windows Server 2022
  • affected>= 10.0.20348.0 and < 10.0.20348.5386
Microsoft Windows Server 2025
  • affected>= 10.0.26100.0 and < 10.0.26100.33158
Microsoft Windows Server 2025 (Server Core installation)
  • affected>= 10.0.26100.0 and < 10.0.26100.33158

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

public exploits

Public exploit code: 1 on Exploit-DB · 3 GitHub proofs of concept

Exploit-DB

Listed so you can judge urgency, not as a recommendation to run anything. GitHub “proofs of concept” are unvetted: some are fake or carry malware. Exploit-DB marks the entries its staff verified.

cisa ssvc

exploitation
active
automatable
no
technical impact
partial

Assessed by CISA 27 Apr 2026 (SSVC 2.0.3).

timeline

  1. 14 Apr 2026Published
  2. 27 Apr 2026CISA SSVC assessment: exploitation active · 12 days later
  3. 28 Apr 2026Added to CISA KEV (exploited in the wild) · 1 day later
  4. 30 Apr 2026First public exploit or proof of concept · 2 days later
  5. 12 May 2026CISA remediation due date (US federal agencies) · 12 days later
  6. 15 Oct 2026CVE record last updated · 157 days (about 5 months) later
  7. 2 Nov 2026Analysed by vulneraibility.com · 18 days later
how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
4 references in the CVE record: 1 patch, 3 links
  • Patchmsrc.microsoft.com /update-guide/vulnerability/CVE-2026-32202
  • Linkcisa.gov /known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-32202
  • Linkvicarius.io /vsociety/posts/cve-2026-32202-detection-script-spoofing-vulnerability-in-window
  • Linkvicarius.io /vsociety/posts/cve-2026-32202-mitigation-script-spoofing-vulnerability-in-windo

sources

get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free

© 2026 vulneraibility.com, all rights reserved