+44 1865 950 828 Secure Your Business
Actively exploited

CVE-2010-2568 Microsoft Windows Remote Code Execution Vulnerability

Microsoft Windows incorrectly parses shortcuts in such a way that malicious code may be executed when the operating system displays the icon of a malicious shortcut file. An attacker who successfully exploited this vulnerability could execute code as the logged-on user.

From the CISA KEV catalogue version 2026.11.06, with Cybergen analysis. Updated 6 Nov 2026.

Our Assessment

Should You Worry?

Patch urgentlyCybergen assessment
  • CISA confirmed exploitation in the wild and added it to the Known Exploited Vulnerabilities catalogue on 15 Sep 2022.
  • Rated High severity (CVSS 7.8, scored by CISA).
  • It has been in the catalogue for 1,513 days. Systems still unpatched now have almost certainly been scanned for it.
The Vulnerability

What It Is

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.

From Watch to Action

What To Do Now

  1. 1

    Find it

    Search your asset inventory and external attack surface for Microsoft Windows. Include cloud images, appliances and anything a supplier runs for you.

    Attack Surface Management
  2. 2

    Fix it

    Apply updates per vendor instructions.

    Vulnerability Management
  3. 3

    Hunt for compromise

    If an affected system was reachable before you patched, assume it may have been hit. Check logs, new accounts, web shells and outbound connections from the date of exposure.

    Incident Response
  4. 4

    Prove it is fixed

    Rescan or test the system after patching. Upgrades that fail silently and forgotten secondary instances are common.

    Penetration Testing

Vendor Advisories

Regulation

The Compliance Clock

Cyber EssentialsRated high, so if it affects devices in your Cyber Essentials scope, the update must be installed within 14 days of the vendor releasing it.NIS2If exploitation causes a significant incident, essential and important entities owe their CSIRT an early warning within 24 hours and a notification within 72 hours.DORAFinancial entities must classify ICT incidents and send an initial notification for a major incident within strict deadlines, with exploited flaws a common cause.US federal (BOD 22-01)Federal civilian agencies had until 6 Oct 2022 to remediate. A sensible benchmark for everyone else.

General guidance, not legal advice. Your obligations depend on your sector, scope and jurisdiction.

Stay Ahead

More Exploited Microsoft Flaws

Get alerts for MicrosoftWe email you when a new Microsoft vulnerability is confirmed as exploited. Add more vendors on Threat Watch.

By signing up you agree to receive Threat Watch alerts. Unsubscribe at any time. See our Privacy Policy.

CVE-2026-96951Microsoft Windows Command Injection VulnerabilityAdded 13 Oct 2026CVE-2026-65660Microsoft SharePoint Code Injection VulnerabilityAdded 25 Sep 2026CVE-2026-81963Microsoft Windows Link Following VulnerabilityAdded 8 Sep 2026CVE-2026-85880Microsoft Windows Heap-Based Buffer Overflow VulnerabilityAdded 8 Sep 2026CVE-2019-1068Microsoft SQL Server Remote Code Execution VulnerabilityAdded 26 Aug 2026CVE-2026-33824Microsoft Internet Key Exchange (IKE) Service Extensions Double Free VulnerabilityAdded 18 Aug 2026

All 390 exploited Microsoft vulnerabilities

Not Sure If You Are Exposed?

Our attack surface and vulnerability teams can check your internet-facing estate for CVE-2010-2568 and every other exploited flaw on the list.

Check My Exposure
Evidence

Sources

  1. CISA Known Exploited Vulnerabilities catalogue
  2. NVD: CVE-2010-2568
  3. CVE record: CVE-2010-2568
  4. FIRST EPSS
  5. docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046
  6. us-cert.gov/cas/techalerts/TA10-222A.html
  7. isc.sans.edu/diary.html?storyid=9181
  8. oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A11564
  9. f-secure.com/weblog/archives/00001986.html
  10. kb.cert.org/vuls/id/940193
  11. krebsonsecurity.com/2010/07/experts-warn-of-new-windows-shortcut-flaw/
  12. secunia.com/advisories/40647