Microsoft updated its warning this week about a security failure in Windows Shell - CVE-2026-32202 - and confirmed that it is already being exploited in the real world. Although the official CVSS score is moderate, the practical importance of this failure lies in its role within an operating chain and in the ease with which it can convert apparently harmless files into uninteracting credentials theft vectors.
In technical terms, vulnerability is a Failed confidence verification when solving UNC routes, which allows an automatic access to a remote resource (e.g. a .cpl file loaded by the Windows Shell mechanism through an SMB access) to trigger a outgoing SMB connection from the victim machine to a server controlled by the attacker. This connection causes a NTLM exchange that can filter the user's Net-NTLMv2 hash, then exploitable by relays or offline attacks. In practice this dynamic reappeared after a partial patch previously applied to CVE-2026-21510, and according to researchers it links the campaign to the group APT28 (Fancy Bear).

The abuse pattern described by discovers combines LNK files (direct accesses) that activate name resolution in Shell's name space and, in turn, load a DLL / CPL from a remote UNC resource. The big threat was not so much the running of direct remote code, but the theft of credentials that facilitates lateral movement and subsequent attacks.. This explains why actors with specific capabilities and objectives, such as APT28, have incorporated these techniques into targeted campaigns in Ukraine and the European Union.
For organizations and managers, the operational implications are clear: patching is necessary but not sufficient. Microsoft already corrected the failure in the most recent monthly patch, so the first mandatory action is to apply security updates on all affected endpoints and servers. In addition, it is appropriate to validate that the patches were correctly deployed and to review the vulnerability indicators in their patch inventory. You can check the Microsoft security guide for this CVE and related updates on the official Microsoft Security Response Center page: Microsoft Security Response Center.

Beyond the patch, there are defensive measures that reduce both the probability and the impact of this type of abuse. Among the most effective are the restriction of outgoing SMB traffic to the Internet (block TCP / 445 from workstations and servers that do not need to communicate externally), the enabling and requirement of SMB signing where it applies, the configuration of group policies that prevent the automatic resolution of UNC routes from unsafe environments and the deactivation of unnecessary services that can solve remote resources. It is also recommended to increase the use of strong and multifactor authentication to mitigate the value of eventually captured hashes.
In the area of detection, security teams should pay attention to unexpected NTLM authentication events towards external domains, UNC resolution attempts towards off-network hosts and execution linked to CPL charges or LNK direct access. EDR / MDR products should block or alert the dynamic load of DLLs from remote sources and typical NTLM relay activity patterns. In-house suppliers and equipment have started to publish technical analyses; to understand the original research and its technical context, the industry research analysis and blog can be consulted on the Akamai site: Akamai Security Blog.
Finally, this series of failures highlights a recurring lesson: partial mitigation can leave residual vectors that sophisticated actors chain with other vulnerabilities. Modern defense requires complete patches, network segmentation, tightening of authentication protocols and continuous monitoring. Audit your SMB output controls, validate SmartScreen settings and other source protections, and treat NTLM hashes as high-risk credentials: assume that, if exposed, they will require rotation and immediate compensatory measures.
Related
More news on the same subject.

18-year-old Ukrainian youth leads a network of infostealers that violated 28,000 accounts and left $250,000 in losses
The Ukrainian authorities, in coordination with US agents. They have focused on an operation of infostealer which, according to the Ukrainian Cyber Police, was allegedly adminis...

The digital signature is in check: Microsoft dismands a service that turned malware into apparently legitimate software
Microsoft announced the disarticulation of a "malware-signing-as-a-service" operation that exploited its device signature system to convert malicious code into seemingly legitim...

A single GitHub workflow token opened the door to the software supply chain
A single GitHub workflow token failed in the rotation and opened the door. This is the central conclusion of the incident in Grafana Labs following the recent wave of malicious ...

WebWorm 2025: the malware that is hidden in Discord and Microsoft Graphh to evade detection
The latest observations by cyber security researchers point to a change in worrying tactics of an actor linked to China known as WebWorm: in 2025 it has incorporated back doors ...

Identity is no longer enough: continuous verification of the device for real-time security
Identity remains the backbone of many security architectures, but today that column is cracking under new pressures: advanced phishing, real-time proxyan authentication kits and...

The dark matter of identity is changing the rules of corporate security
The Identity Gap: Snapshot 2026 report published by Orchid Security puts numbers to a dangerous trend: the "dark matter" of identity - accounts and credentials that are neither ...

PinTheft the public explosion that could give you root on Arch Linux
A new public explosion has brought to the surface again the fragility of the Linux privilege model: the V12 Security team named the failure as PinTheft and published a concept t...