# CVE-2010-2568: Microsoft Windows Remote Code Execution

> Attackers can execute arbitrary code via crafted shortcut files processed by Windows Shell, affecting all supported Windows versions.

- **Severity:** High 7.8 (`CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H`)
- **Exploited in the wild:** Yes, since 15 Sep 2022 (CISA KEV)
- **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:** 22 Jul 2010
- **Updated:** 22 Oct 2025
- **Also known as:** GHSA-6j7w-pxhr-g4pr

## What is CVE-2010-2568?

CVE-2010-2568 is a high-severity code injection vulnerability in Microsoft Windows 7, published on 22 Jul 2010. 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

Windows Shell in Microsoft Windows XP SP3, Server 2003 SP2, Vista SP1 and SP2, Server 2008 SP2 and R2, and Windows 7 allows local users or remote attackers to execute arbitrary code via a crafted (1) .LNK or (2) .PIF shortcut file, which is not properly handled during icon display in Windows Explorer, as demonstrated in the wild in July 2010, and originally reported for malware that leverages CVE-2010-2772 in Siemens WinCC SCADA systems.

## Which versions are affected by CVE-2010-2568?

It affects 5 products.


Products: Microsoft Windows 7, Microsoft Windows Server 2003, Microsoft Windows Server 2008, Microsoft Windows Vista, Microsoft Windows Xp.

## How do I fix CVE-2010-2568?

No fix has been published for CVE-2010-2568 yet. Limit exposure of the affected software until one is available. US federal agencies must fix it by 6 Oct 2022.

## Is CVE-2010-2568 being exploited?

Yes. Attackers have exploited CVE-2010-2568 in the wild since at least 15 Sep 2022.

Public exploit code:

- Microsoft Windows Shell LNK Code Execution (metasploit)
- Microsoft Windows Shell LNK Code Execution (metasploit)
- Microsoft Windows - Automatic .LNK Shortcut File Code Execution (exploitdb)
- Microsoft Windows - Shell LNK Code Execution (MS10-046) (Metasploit) (exploitdb)
- FannyBMP or DementiaWheel Detection Registry Check (metasploit)

## Other vulnerabilities in Microsoft Windows 7

- [CVE-2015-1635](https://insights.sbomify.com/CVE-2015-1635/): Microsoft HTTP.sys Remote Code Execution (critical 9.8, exploited in the wild)
- [CVE-2015-2360](https://insights.sbomify.com/CVE-2015-2360/): Microsoft Win32k Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6324](https://insights.sbomify.com/CVE-2014-6324/): Microsoft Kerberos Key Distribution Center (KDC) Privilege Escalation (high 8.8, exploited in the wild)
- [CVE-2014-6332](https://insights.sbomify.com/CVE-2014-6332/): Microsoft Windows Object Linking & Embedding (OLE) Automation Array Remote Code Execution (high 8.8, exploited in the wild)
- [CVE-2014-4148](https://insights.sbomify.com/CVE-2014-4148/): Microsoft Windows Remote Code Execution (high 8.8, exploited in the wild)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2010-2568 and fix it if it is affected.

What it is: CVE-2010-2568 is a high-severity code injection vulnerability in Microsoft Windows 7, published on 22 Jul 2010. 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: Yes. Attackers have exploited CVE-2010-2568 in the wild since at least 15 Sep 2022.

Affected product: Microsoft Windows 7. 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-2010-2568/ (Markdown: https://insights.sbomify.com/CVE-2010-2568/index.md)
```

## Sources

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

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