cve.bz

CVE-2026-32202 Microsoft Windows Protection Mechanism Failure Vulnerability

4.3 mediumKEVExploitEPSS 71%

Medium (4.3) in Microsoft Windows. In CISA KEV since 2026-04-28. EPSS 71% estimated probability of exploitation activity in the next 30 days.

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

Severity

CVSS 3.1

4.3 medium
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
EPSS
71% (unchanged from 71% a week ago; 4.9% 30 days ago) estimated probability of exploitation activity in the next 30 days; 99th percentile. Scored 2026-11-15. A forecast for this CVE across the internet, not for your own systems.
CISA KEV
listed 2026-04-28, due 2026-05-12
CISA's assessment (SSVC)
Exploitation: active · Automatable: no · Technical impact: partial, assessed 2026-04-27. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWE
CWE-693 Protection Mechanism Failure
OWASP Top 10
A06:2025 Insecure Design
Published
Modified
NVD analysis
Analyzed
Record from
the NVD, synced

Fix and patched versions

Ask an AI about this CVE

Show the promptExplain CVE-2026-32202 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-32202?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-32202?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-32202 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Badge for a README or a site

CVE-2026-32202

An image that stays current: it is drawn from the data each time it is fetched (a host that proxies images, as GitHub does, may show its copy for a while). Markdown:

[![CVE-2026-32202](https://cve.bz/cve/badge/CVE-2026-32202.svg)](https://cve.bz/cve/CVE-2026-32202)

HTML:

<a href="https://cve.bz/cve/CVE-2026-32202"><img src="https://cve.bz/cve/badge/CVE-2026-32202.svg" alt="CVE-2026-32202"></a>

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
Microsoft Windows 10 Version 1607from 10.0.14393.0 before 10.0.14393.9339
Microsoft Windows 10 Version 1809from 10.0.17763.0 before 10.0.17763.9020
Microsoft Windows 10 Version 21H2from 10.0.19044.0 before 10.0.19044.7548
Microsoft Windows 10 Version 22H2from 10.0.19045.0 before 10.0.19045.7548
Microsoft Windows 11 version 23H2from 10.0.22631.0 before 10.0.22631.7376
Microsoft Windows 11 Version 23H2from 10.0.22631.0 before 10.0.22631.7376
Microsoft Windows 11 Version 24H2from 10.0.26100.0 before 10.0.26100.8875
Microsoft Windows 11 Version 25H2from 10.0.26200.0 before 10.0.26200.8875
Microsoft Windows 11 version 26H1from 10.0.28000.0 before 10.0.28000.2525
Microsoft Windows Server 2012from 6.2.9200.0 before 6.2.9200.26226
Microsoft Windows Server 2012 (Server Core installation)from 6.2.9200.0 before 6.2.9200.26226
Microsoft Windows Server 2012 R2from 6.3.9600.0 before 6.3.9600.23291
Microsoft Windows Server 2012 R2 (Server Core installation)from 6.3.9600.0 before 6.3.9600.23291
Microsoft Windows Server 2016from 10.0.14393.0 before 10.0.14393.9339
Microsoft Windows Server 2016 (Server Core installation)from 10.0.14393.0 before 10.0.14393.9339
Microsoft Windows Server 2019from 10.0.17763.0 before 10.0.17763.9020
Microsoft Windows Server 2019 (Server Core installation)from 10.0.17763.0 before 10.0.17763.9020
Microsoft Windows Server 2022from 10.0.20348.0 before 10.0.20348.5386
Microsoft Windows Server 2025from 10.0.26100.0 before 10.0.26100.33158
Microsoft Windows Server 2025 (Server Core installation)from 10.0.26100.0 before 10.0.26100.33158

Linux distributions

DistributionReleasePackageFixed inAdvisory
Alpinev3.20, v3.21, v3.22 and 2 moredotnet8-runtime8.0.26-r0ALPINE-CVE-2026-32202
Alpinev3.21, v3.22, v3.23 and 1 moredotnet9-runtime9.0.15-r0ALPINE-CVE-2026-32202
Alpinev3.23, v3.24dotnet10-runtime10.0.6-r0ALPINE-CVE-2026-32202
Alpaquita25, streamdotnet8-runtime8.0.26-r0BELL-CVE-2026-32202

From the distributions' data via OSV.dev: the Alpine secdb, CC BY-SA 4.0; BellSoft's OSV database, MIT. Modified: reformatted and linked to CVE records. Credits. On the distributions' own pages: Alpine · Alpaquita.

Public exploits

GitHub PoC

Repositories on GitHub named after this CVE or listed for it by the PoC-in-GitHub index. For those marked Harbor Check: matches CVE, Flawharbor read the code and found it implements this CVE's exploitation technique: read, not run, and its dependencies only checked for warning signs, so a pointer and no guarantee. The rest are unverified: some hold a working proof of concept, some nothing useful, and some malware made to look like one. Read the code before you run any of it.

Attack patterns (CAPEC)

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits. More on the page of CWE-693 (17).

References

Check your stackJSON