CVE-2025-59214 is a Windows File Explorer spoofing and sensitive-information-disclosure vulnerability affecting shortcut-file processing. It was reported as a further bypass of prior fixes for CVE-2025-24054 and CVE-2025-50154. File Explorer inconsistently validates shortcut values: icon-path handling receives the intended security check, while a shortcut target containing a UNC path can take a separate existence-check path. That alternate path can initiate NTLM authentication to an attacker-controlled network service and disclose NTLMv2-SSP authentication material without user interaction.
Mallory correlates every CVE against your assets, your vendors, and active adversary campaigns. Know which vulnerabilities matter for you, not just which ones are loud.
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
What an attacker gets, and what they’ve been doing with it.
If you can’t patch tonight, do this now.
Patch, then assume compromise.
No public exploits tracked yet. Mallory keeps watching.
No public exploit code observed for this vulnerability.
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
3 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
A zero-click bypass of prior Windows NTLM credential-leak mitigations. A crafted LNK file with a UNC target can automatically trigger NTLM authentication and disclose NTLMv2-SSP hashes, enabling offline cracking or NTLM relay attacks that may lead to unauthorized access, lateral movement, privilege escalation, or RCE.
Windows File Explorer spoofing issue referenced in the context of preventing NTLM credential leakage / sensitive information leakage over the network.
A Windows File Explorer issue (described as a spoofing issue) that can be leveraged to leak sensitive information (NTLM credentials/hashes) over the network, apparently via preview-related behavior and external path references.
Query your assets running an affected version, and investigate the blast radius.
Every observed campaign linking this CVE to a named adversary.
Malware families riding this exploit, with evidence and IOCs.
YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.
Cross-references every affected SKU, including bundled OEM variants.
Community discussion across Reddit, Mastodon, and other social sources.