CVE-2010-0266

NONECVSS 0.0Weaponized
0.0
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 55%
CISA-KEV: Not listedEPSS: 55%CVSS: —Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

Microsoft Office Outlook 2002 SP3, 2003 SP3, and 2007 SP1 and SP2 does not properly verify e-mail attachments with a PR_ATTACH_METHOD property value of ATTACH_BY_REFERENCE, which allows user-assisted remote attackers to execute arbitrary code via a crafted message, aka "Microsoft Outlook SMB Attachment Vulnerability."

CVSS v3
—
EG Score
0.0(none)
EG Risk
0
EG Risk 0/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. It is distinct from the 0–10 EG Score, which measures severity.

EPSS
98.9%
KEV
Not listed

Published

July 15, 2010

Last Modified

April 29, 2026

References (6)

Weakness Classification(1)

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

Data Freshness Timeline

(refreshed 11× in last 7d / 23× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. 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. Most recent first.

  1. 2026-07-23 14:14 UTCEPSS rescore
  2. 2026-07-23 01:00 UTCEG score recompute
  3. 2026-07-23 00:38 UTCEG score recompute▼ 4.10
  4. 2026-07-23 00:05 UTCEG score recompute▲ 4.10
  5. 2026-07-22 21:44 UTCEG score recompute
  6. 2026-07-22 14:03 UTCEPSS rescore
  7. 2026-07-22 14:03 UTCEPSS rescore
  8. 2026-07-21 15:20 UTCEPSS rescore
  9. 2026-07-20 17:03 UTCEPSS rescore
  10. 2026-07-19 02:25 UTCEPSS rescore
  11. 2026-07-18 10:00 UTCEPSS rescore
  12. 2026-07-15 16:54 UTCEPSS rescore
  13. 2026-07-15 16:54 UTCEPSS rescore
  14. 2026-07-13 06:08 UTCEPSS rescore
  15. 2026-07-11 08:22 UTCEPSS rescore
  16. 2026-07-05 02:26 UTCEPSS rescore
  17. 2026-07-02 14:01 UTCEPSS rescore
  18. 2026-07-01 15:02 UTCEPSS rescore
  19. 2026-06-30 23:19 UTCEPSS rescore
  20. 2026-06-27 03:05 UTCEPSS rescore
  21. 2026-06-25 13:46 UTCEPSS rescore
  22. 2026-06-24 14:02 UTCEPSS rescore
  23. 2026-06-24 14:02 UTCEPSS rescore
  24. 2026-06-23 21:30 UTCEPSS rescore
  25. 2026-06-23 21:29 UTCEPSS rescore
Show 45 more
  1. 2026-06-22 14:22 UTCEPSS rescore
  2. 2026-06-22 14:22 UTCEPSS rescore
  3. 2026-06-21 14:53 UTCEPSS rescore
  4. 2026-06-21 01:56 UTCEPSS rescore
  5. 2026-06-21 01:56 UTCEPSS rescore
  6. 2026-06-18 17:49 UTCEPSS rescore
  7. 2026-06-18 17:49 UTCEPSS rescore
  8. 2026-06-17 17:49 UTCEPSS rescore
  9. 2026-06-17 17:49 UTCEPSS rescore
  10. 2026-06-16 17:49 UTCEPSS rescore
  11. 2026-06-15 17:44 UTCEPSS rescore
  12. 2026-06-14 23:14 UTCEPSS rescore
  13. 2026-06-13 22:57 UTCEPSS rescore
  14. 2026-06-13 22:57 UTCEPSS rescore
  15. 2026-06-13 22:57 UTCEPSS rescore
  16. 2026-06-12 23:08 UTCEPSS rescore
  17. 2026-06-12 23:08 UTCEPSS rescore
  18. 2026-06-11 13:56 UTCEPSS rescore
  19. 2026-06-10 22:14 UTCEPSS rescore
  20. 2026-06-05 22:44 UTCEPSS rescore
  21. 2026-06-05 22:44 UTCEPSS rescore
  22. 2026-06-05 06:07 UTCEPSS rescore
  23. 2026-06-05 06:07 UTCEPSS rescore
  24. 2026-06-04 13:09 UTCEPSS rescore
  25. 2026-06-04 13:09 UTCEPSS rescore
  26. 2026-06-01 13:49 UTCEPSS rescore
  27. 2026-06-01 13:49 UTCEPSS rescore
  28. 2026-05-29 13:40 UTCEPSS rescore
  29. 2026-05-29 10:54 UTCEG score recompute
  30. 2026-05-29 10:53 UTCGHSA enrichment
  31. 2026-05-28 13:42 UTCEPSS rescore
  32. 2026-05-28 13:42 UTCEPSS rescore
  33. 2026-05-27 13:38 UTCEPSS rescore
  34. 2026-05-27 13:38 UTCEPSS rescore
  35. 2026-05-26 07:16 UTCEPSS rescore
  36. 2026-05-26 07:16 UTCEPSS rescore
  37. 2026-05-22 21:15 UTCEPSS rescore
  38. 2026-05-22 21:15 UTCEPSS rescore
  39. 2026-05-22 21:15 UTCEPSS rescore
  40. 2026-05-21 22:39 UTCEPSS rescore
  41. 2026-05-20 22:37 UTCEPSS rescore
  42. 2026-05-20 22:37 UTCEPSS rescore
  43. 2026-05-20 22:37 UTCEPSS rescore
  44. 2026-05-18 21:29 UTCEPSS rescore
  45. 2026-05-18 21:29 UTCEPSS rescore

Publicly available exploits

(4 references)

Working exploit code is in the public domain (2 Metasploit modules) (2 Exploit-DB entries). Defenders should treat patch urgency accordingly — public PoCs typically lead to mass-exploitation within 24-72 hours.

  • Exploit-DBEDB-16699✓ verified
    First seen Sep 20, 2010

    Microsoft Outlook - 'ATTACH_BY_REF_RESOLVE' File Execution (MS10-045) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-16700✓ verified
    First seen Sep 20, 2010

    Microsoft Outlook - 'ATTACH_BY_REF_ONLY' File Execution (MS10-045) (Metasploit)

    Open source ↗
  • Metasploitexploit/windows/email/ms10_045_outlook_ref_only✓ verified
    First seen Jun 1, 2010

    Outlook ATTACH_BY_REF_ONLY File Execution

    Open source ↗
  • Metasploitexploit/windows/email/ms10_045_outlook_ref_resolve✓ verified
    First seen Jun 1, 2010

    Outlook ATTACH_BY_REF_RESOLVE File Execution

    Open source ↗

Related CVEs(same CWE)

Frequently asked(4)

What is CVE-2010-0266?
CVE-2010-0266 is a none vulnerability published on July 15, 2010. Microsoft Office Outlook 2002 SP3, 2003 SP3, and 2007 SP1 and SP2 does not properly verify e-mail attachments with a PRATTACHMETHOD property value of ATTACHBYREFERENCE, which allows user-assisted remote attackers to execute arbitrary code via a crafted message, aka "Microsoft Outlook SMB Attachment…
When was CVE-2010-0266 disclosed?
CVE-2010-0266 was first published in the National Vulnerability Database on July 15, 2010, with the most recent update on April 29, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2010-0266 actively exploited?
CVE-2010-0266 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 98.9% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
How do I remediate CVE-2010-0266?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-0266, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

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

Explore →

Is Your Infrastructure Affected by CVE-2010-0266?

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

Start Free Scan →Browse All CVEs