CVE-2010-2568

CRITICALNVD 7.89.0
EchelonGraph scoreHIGH confidence

“▲” beside the score: it is higher than NVD's CVSS score.

Score elevated to 9.0 because this CVE is listed on the CISA Known Exploited Vulnerabilities catalog (added 2022-09-15), indicating real-world exploitation has been confirmed by US federal agencies. NVD baseline CVSS 7.8 retained for reference. Confidence: HIGH.

Triggered by: CISA KEV (actively exploited)
Sources: CISA Known Exploited Vulnerabilities catalog, EPSS, GitHub Security Advisory, NVD CVSS v3
Trending — 3 sources updated this weekExploited in the wild
9.0EG
EchelonGraph verdictMitigate nowTreat as an emergency — this is being exploited.
  • Actively exploited in the wild (CISA-KEV) — the reason this is sooner than the SSVC decision on this page at low or medium mission impact
CISA-KEV: ExploitedEPSS PROB: 91%CVSS: 7.8Exploit: Metasploit · Exploit-DB (verified)Exposed services: Not assessed

A fix is referenced (a reference tagged "Patch", often a source commit), but no release containing it is confirmed — find the release that contains it; until it is applied, mitigate (WAF / firewall / segmentation).

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.

CVSS v3
7.8
EG Score
9.0CRITICALhigh confidence
EG Risk
81
EG Risk 81/100

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed (value × EchelonGraph’s weight)
Severity90% × 45%
The EG Score, 9.0 of 10.
Exploitation100% × 40%
Fixed at 100% for a CISA KEV listing: EchelonGraph's rule.
Automatability0% × 15%
CISA's SSVC Automatable value: no (Vulnrichment).
SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Attend at medium and Act at high mission impact.
Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE.
Action: A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
EPSS PROB
91%
EPSS %ILE
99th
KEV
⚠ Exploited

SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Attend at medium and Act at high mission impact.

A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that within your standard update timelines at low, sooner than that at medium and as soon as possible at high mission impact; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Exploitation active (CISA Vulnrichment) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). All three are CISA's SSVC values (Vulnrichment). EchelonGraph applied CISA's decision table to them; CISA publishes SSVC inputs and the table, not a decision for each CVE. Mission impact is CISA's Mission & Well-being decision point, and only you can judge it. CISA's table makes it high when Mission Prevalence is Essential — the vulnerable component "directly provides capabilities that constitute at least one MEF for at least one entity" (MEF: mission essential function) — or when Public Well-Being Impact is Irreversible: "multiple fatalities are likely", the cyber-physical system "is likely lost or destroyed", "extreme or serious externalities" are imposed on other parties, or social systems such as elections or the financial grid "are destabilized and potentially collapse". CISA's decision table

BOD 26-04 (CISA's remediation timeline, Table 1)3 days & forensic triage if the affected system is publicly exposed; 14 days if it is not.

In CISA KEV yes (CISA's KEV catalog) · Automatable no (CISA Vulnrichment) · Technical impact total (CISA Vulnrichment). Whether your system is publicly exposed is yours to answer. BOD 26-04 binds US Federal Civilian Executive Branch agencies; for anyone else it is CISA's published timeline, a reference rather than an obligation. The directive · how EchelonGraph applies it

CISA required action“Apply updates per vendor instructions.”

Quoted verbatim from CISA's Known Exploited Vulnerabilities catalog. CISA directs it at US federal civilian executive branch agencies under Binding Operational Directive (BOD) 26-04, which replaced BOD 22-01 on 10 June 2026; it is not EchelonGraph's advice. CISA's notes: https://docs.microsoft.com/en-us/security-updates/securitybulletins/2010/ms10-046 · https://nvd.nist.gov/vuln/detail/CVE-2010-2568

Published

July 22, 2010

Last Modified

April 22, 2026

Advisory Details (7)

Auto-updated May 19, 2026
⚠️ Actively exploited (CISA KEV, CISA Vulnrichment). Fix referenced — no release confirmed yet. Sources: cert.
CERT

VU#940193 - Microsoft Windows automatically executes code specified in shortcut files

http://www.kb.cert.org/vuls/id/940193
Web page

About Secunia Research | Flexera

http://secunia.com/advisories/40647
Web page

Experts Warn of New Windows Shortcut Flaw – Krebs on Security

http://krebsonsecurity.com/2010/07/experts-warn-of-new-windows-shortcut-flaw/
Web page

Preempting a Major Issue Due to the LNK Vulnerability - Raising Infocon to Yellow

http://isc.sans.edu/diary.html?storyid=9190
Web page

Vulnerability in Windows "LNK" files? - SANS ISC

http://isc.sans.edu/diary.html?storyid=9181

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 47× in last 7d / 207× in last 30d)

Each row is a time one of our pipelines fetched, updated or re-scored this CVE. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. An arrow marks a change the record states ("CVSS v3 → 9.1"); EPSS and GHSA rows show the values recorded at that time, not what changed (EPSS values are rounded; hover one for the exact figures). Most recent first.

Showing the most recent 100 of 951 refreshes on record for this CVE.

A repeat, a row identical to one the same pipeline wrote less than 10 seconds earlier, is not a separate refresh and is not counted. None are among the latest 100 rows. The 851 oldest rows on record are not shown and were not checked, so the counts can still include repeats.

  1. 2026-10-12 06:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-12 02:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-11 22:45 UTCEG score recompute
  4. 2026-10-11 22:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-11 18:47 UTCEG score recompute
  6. 2026-10-11 18:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-11 14:44 UTCEG score recompute
  8. 2026-10-11 14:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-11 10:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-11 06:41 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-11 02:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-10 22:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  13. 2026-10-10 18:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-10 14:43 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  15. 2026-10-10 10:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-10 06:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-10 02:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-09 22:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-09 18:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-09 14:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-09 10:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-09 06:35 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-09 02:35 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-08 22:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-08 18:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
Show 75 more
  1. 2026-10-08 14:37 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  2. 2026-10-08 10:35 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  3. 2026-10-08 06:33 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  4. 2026-10-08 02:34 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  5. 2026-10-07 22:35 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  6. 2026-10-07 18:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  7. 2026-10-07 14:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  8. 2026-10-07 10:37 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  9. 2026-10-07 06:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  10. 2026-10-07 02:37 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  11. 2026-10-06 22:37 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  12. 2026-10-06 18:38 UTCEG score recompute
  13. 2026-10-06 18:38 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  14. 2026-10-06 15:09 UTCEPSS rescoreEPSS 91% · 99th percentile
  15. 2026-10-06 14:39 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  16. 2026-10-06 10:40 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  17. 2026-10-06 06:38 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  18. 2026-10-06 02:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  19. 2026-10-05 22:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  20. 2026-10-05 18:36 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  21. 2026-10-05 14:37 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  22. 2026-10-05 10:39 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  23. 2026-10-05 06:40 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  24. 2026-10-05 02:41 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  25. 2026-10-04 22:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  26. 2026-10-04 18:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  27. 2026-10-04 14:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  28. 2026-10-04 10:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  29. 2026-10-04 06:43 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  30. 2026-10-04 02:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  31. 2026-10-03 22:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  32. 2026-10-03 18:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  33. 2026-10-03 14:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  34. 2026-10-03 10:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  35. 2026-10-03 06:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  36. 2026-10-03 02:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  37. 2026-10-02 22:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  38. 2026-10-02 18:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  39. 2026-10-02 14:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  40. 2026-10-02 10:48 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  41. 2026-10-02 06:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  42. 2026-10-02 02:48 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  43. 2026-10-01 22:45 UTCEG score recompute
  44. 2026-10-01 22:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  45. 2026-10-01 18:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  46. 2026-10-01 14:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  47. 2026-10-01 10:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  48. 2026-10-01 06:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  49. 2026-10-01 02:45 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  50. 2026-09-30 22:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  51. 2026-09-30 18:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  52. 2026-09-30 14:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  53. 2026-09-30 10:48 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  54. 2026-09-30 06:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  55. 2026-09-30 02:46 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  56. 2026-09-29 22:47 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  57. 2026-09-29 18:43 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  58. 2026-09-29 14:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  59. 2026-09-29 10:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  60. 2026-09-29 06:38 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  61. 2026-09-29 02:39 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  62. 2026-09-28 22:40 UTCEG score recompute
  63. 2026-09-28 22:40 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  64. 2026-09-28 18:41 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  65. 2026-09-28 14:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  66. 2026-09-28 10:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  67. 2026-09-28 06:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  68. 2026-09-28 02:41 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  69. 2026-09-27 22:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  70. 2026-09-27 21:51 UTCCISA KEV update
  71. 2026-09-27 18:43 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  72. 2026-09-27 14:44 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  73. 2026-09-27 10:43 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  74. 2026-09-27 06:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8
  75. 2026-09-27 02:42 UTCGHSA enrichmentGHSA-6j7w-pxhr-g4pr · GitHub severity HIGH · GitHub CVSS 7.8

Publicly available exploits

(5 references)

Public exploit code is referenced for this CVE (3 Metasploit modules, 2 Exploit-DB entries). No release with the fix is confirmed, so defenders should restrict or isolate affected systems accordingly until one is applied.

  • Metasploitpost/windows/gather/forensics/fanny_bmp_check✓ verified
    Published Jan 25, 2021

    FannyBMP or DementiaWheel Detection Registry Check

    Open source ↗
  • Metasploitexploit/windows/smb/ms10_046_shortcut_icon_dllloader✓ verified
    Published Mar 12, 2015

    Microsoft Windows Shell LNK Code Execution

    Open source ↗
  • Exploit-DBEDB-16574✓ verified
    Published Sep 21, 2010

    Microsoft Windows - Shell LNK Code Execution (MS10-046) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/browser/ms10_046_shortcut_icon_dllloader✓ verified
    Published Aug 4, 2010

    Microsoft Windows Shell LNK Code Execution

    Open source ↗
  • Exploit-DBEDB-14403✓ verified
    Published Jul 18, 2010

    Microsoft Windows - Automatic .LNK Shortcut File Code Execution

    Open source ↗

Frequently asked(6)

What is CVE-2010-2568?
CVE-2010-2568 is a critical-severity vulnerability; its CVE record was published on July 22, 2010. 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…
When was CVE-2010-2568 made public?
CVE-2010-2568 was made public on July 16, 2010: that is the date its CVE record's CNA, Microsoft Corporation, gives for when the vulnerability was made public. The CVE record itself was published on July 22, 2010. EchelonGraph's copy of the record carries a last-modified date of April 22, 2026; the record at its source may have been updated since.
Is CVE-2010-2568 actively exploited?
Yes. CISA added CVE-2010-2568 to the Known Exploited Vulnerabilities catalog on September 15, 2022, affecting Microsoft Windows. KEV listing indicates confirmed exploitation in the wild; this CVE warrants immediate attention. A fix is referenced, but no release containing it is confirmed. Check the referenced fix and the vendor's advisory for a release that contains it and apply that; until then, restrict network exposure of the affected system or apply the vendor's mitigation.
What is the CVSS score of CVE-2010-2568?
CVE-2010-2568 has a CVSS v3 base score of 7.8 (NVD). EchelonGraph synthesises NVD + CISA KEV + FIRST EPSS + GHSA into a combined EG score of 9.0 (CRITICAL).
Which products are affected by CVE-2010-2568?
CVE-2010-2568 affects Microsoft Windows.
How do I remediate CVE-2010-2568?
A fix for CVE-2010-2568 is referenced (a reference tagged "Patch", often a source commit), but EchelonGraph has no release containing it on record. Check that reference and the vendor's advisory for a release that contains the fix and update to it; until then, restrict network exposure of the affected system or apply the vendor's mitigation.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2010-2568

Explore →

Is Your Infrastructure Affected by CVE-2010-2568?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.