Skip to main content
Mallory
MediumExploited in the wildCISA KEVPublic exploitVulnerability

CVE-2026-32202: Zero-click NTLM authentication coercion in Microsoft Windows Shell

Published Apr 14, 2026 · Updated today
Trending this weekNot trendingOutside this week’s top 100
Mention activity · 30 days4 mentions · peak 2 in a dayToday
CVSS4.3Medium · v3.1
EPSS71.3%99th percentile
CISA KEVYesAdded Apr 28, 2026
In the wildActivePer CISA KEV
Vendor
Microsoft Corporation
IdentifiersCVE-2026-32202CWE-693 · Protection Mechanism Failure

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.

Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Analyst brief

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.

Public exploits

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.

View more in app →
CVE-2026-32202Repository contains a single Python proof-of-concept script and a detailed README. The main file, CVE-2026-32202.py, is a research-oriented generator for crafted Windows .lnk files that reproduce the LinkTargetIDList structure associated with CVE-2026-21510 / CVE-2026-32202. The script reconstructs three shell items: (1) a Control Panel root CLSID item, (2) an 'All Control Panel Items' category item, and (3) a Unicode _IDCONTROLW structure containing a user-supplied module path, typically a UNC path to a remote .cpl file. It exposes CLI options for the embedded UNC/local path, output filename, applet ID, display name, infotip, and optional hex dump suppression. The exploit capability is file generation rather than direct network communication; however, the generated LNK is intended to cause Windows Explorer/shell32 to access the embedded UNC path during rendering, which can coerce outbound SMB authentication or connection to an attacker-controlled share. The README provides reverse-engineering context, structure layouts, call-chain analysis, and explains that the vulnerable behavior occurs before later trust verification stages. Overall, this is a focused PoC/research tool for crafting malicious shortcut files to reproduce Windows shell path-resolution behavior, not a full weaponized framework or post-exploitation implant.virus-or-not · Disclosed Apr 30, 2026 · python · markdown · file · network · wirelessPoCCVE-2026-32202This repository is a small proof-of-concept consisting of a README and one Python script, poc.py. The script builds a malicious Windows .lnk shortcut file from scratch using Python struct packing. Its purpose is to coerce Windows Explorer into initiating an outbound SMB connection during icon resolution, without the victim needing to open the shortcut. The README explains the underlying behavior: Explorer traverses Control Panel shell item handling, eventually checking whether a module path exists; if that module path is a UNC path, Windows performs a remote file attribute/stat operation that opens SMB to the attacker and triggers automatic NTLM authentication. The exploit structure is straightforward: build_header() creates a Shell Link header, shitemid_clsid() creates CLSID-based shell items, shitemid_unicode_cpl() creates a crafted Unicode Control Panel applet item with the attacker-controlled module path at offset +0x18, build_idlist() chains the Control Panel CLSID, All Control Panel Items CLSID, and malicious CPL item into a LinkTargetIDList, and build_lnk() assembles the final .lnk bytes. main() exposes CLI arguments for the UNC path and output filename, then writes the malicious shortcut. Primary capability: generation of a crafted .lnk file that causes zero-click credential coercion when merely viewed in Explorer. The practical result is outbound SMB authentication to an attacker-controlled host, leaking Net-NTLMv2 material. There is no post-exploitation shell or code execution payload in the repository; it is focused on credential leakage/coercion via a malicious file and remote UNC path.alexlanum · Disclosed Jun 21, 2026 · python · markdown · file · network · webPoC
Exposure surface

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.

VendorProductType
Microsoft CorporationWindows 10 1607operating_system
Microsoft CorporationWindows 10 1809operating_system
Microsoft CorporationWindows 10 21h2operating_system
Microsoft CorporationWindows 10 22h2operating_system
Microsoft CorporationWindows 11 23h2operating_system
Microsoft CorporationWindows 11 24h2operating_system
Microsoft CorporationWindows 11 25h2operating_system
Microsoft CorporationWindows 11 26h1operating_system
Microsoft CorporationWindows Server 2012operating_system
Microsoft CorporationWindows Server 2012 R2operating_system
Microsoft CorporationWindows Server 2016operating_system
Microsoft CorporationWindows Server 2019operating_system
Microsoft CorporationWindows Server 2022operating_system
Microsoft CorporationWindows Server 2022 23h2operating_system
Microsoft CorporationWindows Server 2025operating_system
Microsoft CorporationWindows Server 23h2operating_system
FAQ

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.
Activity feed

Recent activity

142 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.

View more in app →
threathunter ai blogNews · Nov 11, 2026November 2026 Patch Tuesday: 1,235 fixes and the Outlook hash thief | ThreatHunter.aiA Windows Shell NTLM disclosure vulnerability cited as historical precedent. The content says remediation required two patches but does not establish exploitation of this specific flaw.Read more ↗help net securityNews · Oct 20, 2026Incomplete security patches show hackers where to look next - Help Net SecurityA bypass of the patch for Windows Shell vulnerability CVE-2026-21510. A crafted Control Panel item could make Windows contact an attacker-controlled server and leak the user's NTLM hash. Microsoft patched the bypass in April 2026, and it was subsequently included in CISA's Known Exploited Vulnerabilities catalog.Read more ↗register securityNews · Oct 19, 2026Security patches need patches now that attackers have AIA zero-click authentication coercion vulnerability left unresolved by Microsoft's incomplete patch for CVE-2026-21510. It was discovered and exploited before Microsoft fixed it in April 2026, illustrating the risks of incomplete security fixes.Read more ↗0patch blogNews · Jul 20, 2026Broken official patches for Windows Shell Spoofing Vulnerability (CVE-2026-32202)A Windows Shell vulnerability that leaks NTLM credentials when a user views a network folder containing a malicious LNK file. The article reports that Microsoft's April 2026 fix works on Windows Server 2025 and Windows 11 24H2/25H2, but remains bypassable on several other supported releases even with June 2026 updates. The researchers reproduced the bypass with a proof of concept and released third-party micropatches for affected supported and legacy versions. In-the-wild exploitation is reported tentatively, without identifying attackers or malware.Read more ↗
+15 more in the timeline. Sign up to see them
Do you run this?See affected versions in your environment and whether adversaries are exploiting this vulnerability against assets like yours.
Check your exposure
Mallory platform

The version that knows your environment.

This page is what’s public. Mallory adds the parts that aren’t: which of your assets are affected, which adversaries are exploiting it right now, and which detections to deploy tonight.
Exposure mappingQuery your assets running an affected version, and investigate the blast radius.
Threat actor evidence3Every report linking this CVE to a named adversary.
Associated malware1Malware families linked to this CVE, with evidence and IOCs.
Detection signatures2YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Vendor-by-vendor mappingCross-references every affected SKU, including bundled OEM variants.
Social activity120Community discussion across Reddit, Mastodon, and other social sources.