Microsoft Windows LNK File UI Misrepresentation Remote Code Execution Vulnerability
CVE-2025-9491 is a Microsoft Windows vulnerability in the handling of .LNK shortcut files. The flaw is a UI misrepresentation issue in which crafted shortcut data can cause hazardous content—specifically malicious command-line arguments or other execution-relevant target information—to be hidden or not fully shown in the Windows-provided user interface when a user inspects the shortcut. Multiple supporting sources describe the core issue as Windows Explorer historically displaying only the first 260 characters of a shortcut Target field, allowing attackers to pad the command line with whitespace so the malicious portion remains invisible in Properties while the full command is still executed. Successful exploitation can therefore trick a user into opening what appears to be a benign shortcut, resulting in arbitrary code execution in the context of the current user. ZDI tracked the issue as ZDI-25-148 / ZDI-CAN-25373.
Are you exposed to this one?
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.
Impact, mitigation & remediation
What it means. What to do now. Patch path, mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Mitigation
If you can’t patch tonight, do this now.
Remediation
Patch, then assume compromise.
Exploits
1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.
This repository is a proof-of-concept (PoC) tool for CVE-2025-9491, a Windows UI misrepresentation vulnerability affecting .lnk (shortcut) files. The repository contains three files: a detailed README.md, the main exploit script (main.py), and a requirements.txt specifying the pylnk3 library. The main.py script is a Python tool that allows users to create new .lnk files with obfuscated (whitespace-padded) arguments, obfuscate existing .lnk files, or parse and display the contents of .lnk files. The exploit leverages the fixed-size 'Target' field in Windows shortcut properties, using whitespace padding to hide malicious command-line arguments from users inspecting the shortcut. The tool supports various padding patterns and custom character sets for obfuscation. The primary attack vector is local: the attacker must convince a user to open or inspect a malicious .lnk file, which can then execute hidden commands. The tool does not provide a remote shell or network-based payload, but enables stealthy local execution of arbitrary commands via shortcut files. The repository is well-documented and structured, with the main exploit logic contained in main.py.
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.
Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.
Recent activity
85 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.
Windows Shortcut (LNK) UI misinterpretation vulnerability leading to remote code execution; exploited by multiple threat actors since 2017; patched in Nov 2025 updates.
A Windows LNK (shortcut) file spoofing/obfuscation vulnerability that can be exploited to hide command-line arguments (via excessive whitespace padding), enabling deceptive shortcuts that appear benign while executing malicious commands.
A Windows Explorer LNK UI deception issue where long command-line arguments in shortcut files are truncated in the Target field, enabling attackers to hide malicious arguments from users inspecting shortcut properties.
A vulnerability in the handling of .LNK files in Windows, potentially allowing attackers to exploit shortcut files for malicious purposes.
The version that knows your environment.
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.