CVE-2026-32202: Zero-click NTLM authentication coercion in Microsoft Windows Shell
- Vendor
- Microsoft Corporation
CVE-2026-32202 is a protection mechanism failure in Microsoft Windows Shell that permits unauthenticated network attackers to coerce NTLM authentication through a specially crafted Windows shortcut. The vulnerability remained after the incomplete February 2026 fix for CVE-2026-21510: execution-time trust verification blocked the original code-execution path but did not prevent earlier network access during shortcut icon extraction. When Windows Explorer renders a folder containing the malicious shortcut, a crafted LinkTargetIDList referencing a Control Panel COM object causes resolution of an attacker-controlled UNC location. The icon-extraction path through CControlPanelFolder::GetUIObjectOf and GetModuleMapped invokes PathFileExistsW, initiating an SMB connection and automatic NTLM authentication before the relevant trust checks. This can expose the user's Net-NTLMv2 challenge-response material without opening or executing the shortcut. Microsoft confirmed active exploitation, and CISA added the vulnerability to its Known Exploited Vulnerabilities catalog on April 28, 2026.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation exposes Net-NTLMv2 authentication material associated with the victim's account. Attackers may relay the authentication to services that accept NTLM without effective relay protections, or attempt offline password cracking. Successful follow-on attacks can permit user impersonation, unauthorized access to sensitive information and network resources, and lateral movement within the victim account's privileges. Captured challenge-response material is not itself a plaintext password, and subsequent compromise depends on password strength, reachable services, and authentication protections. This vulnerability alone does not establish arbitrary code execution; the earlier code-execution and SmartScreen-bypass chain involved separate vulnerabilities.
Mitigation
If you can’t patch tonight, do this now.
Block outbound SMB traffic to untrusted networks at the network perimeter where feasible to prevent the described authentication-coercion path. Reduce NTLM exposure and monitor unexpected outbound SMB connections and NTLM authentication to untrusted servers. Where an effective Microsoft fix is unavailable, consider the applicable 0patch micropatch after compatibility and deployment validation; these micropatches specifically constrain shortcut processing involving the Control Panel COM object. Network restrictions reduce exposure but do not replace validated remediation, particularly when attacker-controlled destinations are reachable internally.
Remediation
Patch, then assume compromise.
Apply Microsoft's security updates addressing CVE-2026-32202, initially released on April 14, 2026, and applicable superseding updates. Validate remediation on each operating-system version rather than relying solely on update installation or scanner results. June 12 testing found the April fix bypassable even after June updates on Windows 10 22H2 with Extended Security Updates, Windows 11 23H2, and Windows Server 2012/2012 R2 through 2022. The fix was reported effective on Windows Server 2025 and Windows 11 24H2 and 25H2. The added MapUrlToZoneEx check in ShellLink::_InitExtractIcon could be bypassed because of surrounding code logic on affected versions. 0patch released alternative micropatches for multiple supported and legacy Windows releases. Confirmation of a subsequent complete Microsoft fix for every affected release is not available in the supplied information. Follow current Microsoft instructions and discontinue use of affected systems if effective remediation or mitigation cannot be deployed.
Exploits
2 exploits validated by Mallory's analysis. Hidden: 1 rejected by Mallory's analysis as not a working exploit; 1 not yet analyzed, such as Exploit-DB entries.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
References
Frequently asked questions
- Is CVE-2026-32202 exploited in the wild?
- Yes. As of Nov 17, 2026, Mallory has reports of exploitation in the wild, and CISA added it to KEV on Apr 28, 2026.
- Is there a public exploit for CVE-2026-32202?
- Yes. Mallory tracks 2 public exploits or proofs of concept for CVE-2026-32202, the earliest disclosed Apr 30, 2026.
- Is there a patch for CVE-2026-32202?
- Apply Microsoft's security updates addressing CVE-2026-32202, initially released on April 14, 2026, and applicable superseding updates. Validate remediation on each operating-system version rather than relying solely on update installation or scanner results.
- What products are affected by CVE-2026-32202?
- Microsoft Corporation Windows 10 1607, Microsoft Corporation Windows 10 1809, Microsoft Corporation Windows 10 21h2, Microsoft Corporation Windows 10 22h2, Microsoft Corporation Windows 11 23h2, and 11 more.
- How severe is CVE-2026-32202?
- CVE-2026-32202 has a CVSS v3.1 score of 4.3 (Medium) and an EPSS score of 71.3% (99th percentile) as of Nov 17, 2026.
Recent activity
142 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.