# CVE-2025-9491: Microsoft Windows LNK File UI Misrepresentation Remote Code Execution Vulnerability

> Attackers can hide malicious content in LNK files via UI misrepresentation, leading to arbitrary code execution when users open the file.

- **Severity:** High 7.0 (`CVSS:3.0/AV:L/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Local or same network only
- **Victim action needed:** A user has to click or open something
- **Fix available:** No
- **Published:** 26 Aug 2025
- **Updated:** 5 Dec 2025
- **Also known as:** GHSA-6rf6-f9qg-8v94

## What is CVE-2025-9491?

CVE-2025-9491 is a high-severity vulnerability in Microsoft Windows 11 23h2, published on 26 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.

### Official description

Microsoft Windows LNK File UI Misrepresentation Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of Microsoft Windows. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file.

The specific flaw exists within the handling of .LNK files. Crafted data in an .LNK file can cause hazardous content in the file to be invisible to a user who inspects the file via the Windows-provided user interface. An attacker can leverage this vulnerability to execute code in the context of the current user. Was ZDI-CAN-25373.

Weakness: CWE-451 (User Interface (UI) Misrepresentation of Critical Information)

## Which versions are affected by CVE-2025-9491?

It affects 1 product.


Products: Microsoft Windows 11 23h2.

## How do I fix CVE-2025-9491?

No fix has been published for CVE-2025-9491 yet. Limit exposure of the affected software until one is available.

## Is CVE-2025-9491 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9491 exists.

Public exploit code:

- Proof-of-Concept of the CVE-2025-9491 using invisible characters in the arguments of a Windows shortcut file (.lnk) (github_poc): https://github.com/Amperclock/CVE-2025-9491_POC

## Other vulnerabilities in Microsoft Windows 11 23h2

- [CVE-2026-81963](https://insights.sbomify.com/CVE-2026-81963/): Microsoft Windows Link Following (high 7.8, exploited in the wild)
- [CVE-2026-100219](https://insights.sbomify.com/CVE-2026-100219/): Microsoft QUIC Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-96909](https://insights.sbomify.com/CVE-2026-96909/): Windows BitLocker Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-62815](https://insights.sbomify.com/CVE-2026-62815/): Microsoft QUIC Remote Code Execution Vulnerability (critical 9.8)
- [CVE-2026-45657](https://insights.sbomify.com/CVE-2026-45657/): Windows Kernel Remote Code Execution Vulnerability (critical 9.8)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2025-9491 and fix it if it is affected.

What it is: CVE-2025-9491 is a high-severity vulnerability in Microsoft Windows 11 23h2, published on 26 Aug 2025. It can only be exploited from the same machine or local network, and only if a user opens a file or follows a link.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2025-9491 exists.

Affected product: Microsoft Windows 11 23h2. No package-level version data is available, so check the vendor advisory linked from the reference page.

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2025-9491/ (Markdown: https://insights.sbomify.com/CVE-2025-9491/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2025-9491
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2025-9491
- OSV: https://osv.dev/vulnerability/CVE-2025-9491

---
From sbomify Insights: https://insights.sbomify.com/CVE-2025-9491/
Summaries are generated and may contain mistakes; the official description above is the record.