Skip to main content
Mallory
MediumPublic exploit

Microsoft Windows LNK File UI Misrepresentation Remote Code Execution Vulnerability

IdentifiersCVE-2025-9491CWE-451· User Interface (UI)…Also known aszdi_25_148zdi_can_25373

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.

Share:
For your environment

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.

ANALYST BRIEF

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.

An attacker can achieve arbitrary code execution as the current user by convincing the victim to open a crafted .LNK file or otherwise interact with attacker-controlled content that triggers the shortcut. In observed campaigns, the flaw was used as a social-engineering and defense-evasion mechanism to conceal malicious execution chains, including PowerShell-based downloaders, DLL side-loading, and deployment of malware such as PlugX, Ursnif, Gh0st RAT, and Trickbot. The practical impact includes initial access, malware execution, persistence, espionage-oriented collection, and follow-on compromise of the victim environment, limited by the privileges of the user who launches the shortcut.

Mitigation

If you can’t patch tonight, do this now.

Until all systems are remediated, restrict or block .LNK files from untrusted sources, especially via email, archives, web downloads, and user-writable locations. Enforce Mark-of-the-Web-aware controls, Smart App Control, and Microsoft Defender protections where available. Consider email gateway blocking or sandboxing of .LNK attachments, application allow-listing, and monitoring for suspicious shortcut execution chains such as explorer.exe launching PowerShell, rundll32, mshta, or signed binaries that side-load same-directory DLLs. Hunt for unusually long LNK Target strings, excessive whitespace padding, hidden command-line arguments, and suspicious DLL loads from nonstandard directories. User awareness remains relevant because exploitation requires the victim to open or otherwise interact with the malicious shortcut.

Remediation

Patch, then assume compromise.

Apply Microsoft's fix for CVE-2025-9491 in supported Windows versions. Supporting content indicates Microsoft modified Windows shortcut behavior so the full Target command and arguments are displayed in the Properties dialog rather than truncating at 260 characters. Organizations should ensure affected Windows endpoints are updated to the vendor-corrected builds and verify that the relevant Windows updates addressing Advisory 25258226 / CVE-2025-9491 have been deployed. If vendor patching is not available for a given platform, use compensating controls such as third-party micropatching where appropriate.
PUBLIC EXPLOITS

Exploits

1 valid exploit after Mallory filtered fakes, detection scripts, and README-only repos.

VALID 1 / 1 TOTALView more in app
CVE-2025-9491_POCMaturityPoCVerified exploit

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.

AmperclockDisclosed Nov 7, 2025pythonlocal
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 11 23h2operating_system

Vendor-confirmed product mapping. Mallory continuously reconciles this list against your asset inventory.

What this page doesn’t show

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, which detections to deploy, and what to do tonight.
Exposure mapping

Query your assets running an affected version, and investigate the blast radius.

Threat actor evidence248

Every observed campaign linking this CVE to a named adversary.

Associated malware15

Malware families riding this exploit, with evidence and IOCs.

Detection signatures

YARA, Sigma, Snort, and vendor rules, auto-deployed to your SIEM.

Vendor-by-vendor mapping

Cross-references every affected SKU, including bundled OEM variants.

Social activity65

Community discussion across Reddit, Mastodon, and other social sources.