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

What it is

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

Description quoted from the CVE record (assigned by microsoft, published 2026-04-14).

Weakness: CWE-693: Protection Mechanism Failure

How it can be exploited

Exploitable over the network with low attack complexity needing no privileges and a user must take an action. Impact: confidentiality low, integrity none, availability none. CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N/E:F/RL:O/RC:C

CISA assessment (SSVC): CISA assesses exploitation as active. Automatable: no. Technical impact: partial.

On CISA KEV since

2026-04-28

US federal deadline

2026-05-12

Ransomware use

Not known

Public exploit evidence (Exploit Observer)

Also known as: BDU:2026-05493, CNVD-2026-20178, EDB-52601, EUVD-2026-22589, GHSA-x62h-w968-3v9v

VEDAS cluster: VEDAS:FOXLIGHTFLARE

Exploit Observer links 7 pieces of public exploit code or detection modules that name this CVE or one of its aliases.

Exploit code and modules (7)

Code that names this CVE. A repository can be a working exploit, a scanner, a fake or malware; read it before running anything.

• Exploit-DB: https://www.exploit-db.com/raw/52601
• Code repository: https://github.com/alexlanum/cve-2026-32202
• Code repository: https://github.com/asdrf5gh67j8ki/cve-2026-32202
• Code repository: https://github.com/f0xox/cve-2026-32202
• Code repository: https://github.com/foxfxfxx/cve-2026-32202
• Code repository: https://github.com/solarlynxsqueeze/cve-2026-32202
• Code repository: https://github.com/virus-or-not/cve-2026-32202

Research and write-ups (1)

• Research or write-up: https://www.akamai.com/blog/security-research/2026/apr/incomplete-patch-apt28s-zero-day-cve-2026-32202

Vulnerability databases and vendor advisories (8)

Catalogue entries, not exploit evidence.

• Vulnerability database or vendor advisory: https://euvd.enisa.europa.eu/enisa/EUVD-2026-22589
• Vulnerability database or vendor advisory: https://github.com/advisories/GHSA-x62h-w968-3v9v
• Vulnerability database or vendor advisory: https://msrc.microsoft.com/update-guide/en-US/vulnerability/CVE-2026-32202
• Vulnerability database or vendor advisory: https://nvd.nist.gov/vuln/detail/CVE-2026-32202
• Vulnerability database or vendor advisory: https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-32202
• Vulnerability database or vendor advisory: https://www.cnvd.org.cn/flaw/show/CNVD-2026-20178
• Vulnerability database or vendor advisory: https://www.vicarius.io/vsociety/posts/cve-2026-32202-detection-script-spoofing-vulnerability-in-windows-shell
• Vulnerability database or vendor advisory: https://www.vicarius.io/vsociety/posts/cve-2026-32202-mitigation-script-spoofing-vulnerability-in-windows-shell

5 more references returned by Exploit Observer did not name this CVE or an alias, so they are left out.

VEDAS data as of 2026-11-01T17:12 UTC; fetched 2026-11-02.

Live scores

EPSS

0.709
very likely to be attacked soon

VEDAS

0.978
strong exploit evidence

On CISA KEV

Yes, since 2026-04-28

Detection rule

None yet

Thin horizontal line: the “likely” (EPSS 0.10) or “strong” (VEDAS 0.90) threshold. Shaded “no data” areas are periods when cve-scores did not publish.

Who is affected

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

Exploit Observer also maps it to: microsoft windows_10_1607, microsoft windows_10_1809, microsoft windows_10_21h2, microsoft windows_10_22h2, microsoft windows_11_23h2, microsoft windows_11_24h2, microsoft windows_11_25h2, microsoft windows_11_26h1, microsoft windows_server_2012, microsoft windows_server_2016.

How to fix it

Fixed versions stated in the CVE record: 10.0.14393.9339, 10.0.17763.9020, 10.0.19044.7548, 10.0.19045.7548, 10.0.22631.7376, 10.0.26100.8875, 10.0.26200.8875, 10.0.28000.2525, 6.2.9200.26226, 6.3.9600.23291, 10.0.20348.5386, 10.0.26100.33158.

CISA 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.

Vendor guidance:

• Windows Shell Spoofing Vulnerability (vendor-advisory, patch)

How to detect it

There is no open VEDAS detection rule for this bug yet. It is listed on the detection gaps page if CISA has confirmed attacks.

References

Vendor advisories and patches

• Windows Shell Spoofing Vulnerability (vendor-advisory, patch)

Government sources

• https://www.cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2026-32202 (government-resource)

Other references

• https://www.vicarius.io/vsociety/posts/cve-2026-32202-detection-script-spoofing-vulnerability-in-windows-shell
• https://www.vicarius.io/vsociety/posts/cve-2026-32202-mitigation-script-spoofing-vulnerability-in-windows-shell

Other databases

• CVE record (cve.org)
• NVD
• Exploit Observer

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, CISA KEV, cve-scores (EPSS and VEDAS), Exploit Observer. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.