CVE-2010-1240

HIGHCVSS v2 · 9.39.3—
EchelonGraph scoreLOW confidence

This CVE was only ever scored under CVSS v2.0. NVD CVSS v2.0 base 9.3 — v2 rates that HIGH (v2 bands: LOW 0.0–3.9 / MEDIUM 4.0–6.9 / HIGH 7.0–10.0; v2 has no CRITICAL band). Vector AV:N/AC:M/Au:N/C:C/I:C/A:C. CVSS v2 is an older, coarser metric than v3.1/v4.0 (no Scope, no User Interaction, no Attack Requirements), so it is not directly comparable to a v3 or v4 score. NVD has never re-scored this record under v3. EPSS predicts 73.4% exploitation probability in the next 30 days, which is reflected in EG Risk but does not lift the v2 base. Confidence: LOW.

Sources: epss, nvd_v2
Weaponized
9.3EG
EchelonGraph verdictPatch this weekExploitation is likely or a public exploit exists.
  • High exploitation likelihood — EPSS 74%
  • Public exploit code is available (Metasploit, Exploit-DB (verified), epss top5pct, epss high, public exploit)
CISA-KEV: Not listedEPSS PROB: 74%CVSS v2: 9.3Exploit: Metasploit · Exploit-DB (verified) · epss top5pct · epss high · public exploitExposed: 0

A fix is available — apply it.

Adobe Reader and Acrobat 9.x before 9.3.3, and 8.x before 8.2.3 on Windows and Mac OS X, do not restrict the contents of one text field in the Launch File warning dialog, which makes it easier for remote attackers to trick users into executing an arbitrary local program that was specified in a PDF document, as demonstrated by a text field that claims that the Open button will enable the user to read an encrypted message.

CVSS v2.0 (legacy)
9.3HIGHNVD never assigned a CVSS v3 rating to this CVE
EG Score
9.3(low)
EG Risk
76(Track)
EG Risk 76/100SSVC: Track

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
Severity93% × 45%
Exploitation73% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
74%
EPSS %ILE
99%
KEV
Not listed

Published

April 5, 2010

Last Modified

April 29, 2026

References (16)

Patch Availability(1)

Vendor / EcosystemFixed in / PatchReleasedSource
redhatacroread-0:9.3.3-1.el52010-06-30redhat

Patches are aggregated from vendor advisories (Red Hat, Microsoft, Cisco, GitHub) and package ecosystems (OSV, GHSA). Multiple rows for the same upstream release have been deduplicated.

All Vendor Advisories

(1)

Every vendor that published an advisory referencing this CVE — pulled from our cve_vendor_advisories aggregation. Click any row for the vendor's original advisory page.

Data Freshness Timeline

(refreshed 1× in last 7d / 9× 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-08-26 14:40 UTCEPSS rescore
  2. 2026-08-19 16:58 UTCEPSS rescore
  3. 2026-08-16 02:09 UTCEPSS rescore
  4. 2026-08-15 01:25 UTCEPSS rescore
  5. 2026-08-09 13:41 UTCEPSS rescore
  6. 2026-08-07 16:21 UTCEPSS rescore
  7. 2026-08-06 13:41 UTCEPSS rescore
  8. 2026-08-05 19:11 UTCEPSS rescore
  9. 2026-08-04 15:04 UTCEPSS rescore
  10. 2026-07-26 13:40 UTCEG score recompute▲ 9.30
  11. 2026-07-25 14:12 UTCEPSS rescore
  12. 2026-07-23 14:14 UTCEPSS rescore
  13. 2026-07-23 01:01 UTCEG score recompute
  14. 2026-07-23 00:38 UTCEG score recompute▼ 7.10
  15. 2026-07-23 00:05 UTCEG score recompute▲ 7.10
  16. 2026-07-22 21:44 UTCEG score recompute▼ 9.00
  17. 2026-07-22 14:03 UTCEPSS rescore
  18. 2026-07-22 14:03 UTCEPSS rescore
  19. 2026-07-21 15:20 UTCEPSS rescore
  20. 2026-07-20 17:03 UTCEPSS rescore
  21. 2026-07-15 16:54 UTCEPSS rescore
  22. 2026-07-15 16:54 UTCEPSS rescore
  23. 2026-07-15 01:55 UTCEPSS rescore
  24. 2026-07-13 06:08 UTCEPSS rescore
  25. 2026-07-08 15:10 UTCEPSS rescore
Show 45 more
  1. 2026-07-08 15:10 UTCEPSS rescore
  2. 2026-07-06 02:19 UTCEPSS rescore
  3. 2026-07-06 02:19 UTCEPSS rescore
  4. 2026-07-02 14:01 UTCEPSS rescore
  5. 2026-07-01 15:02 UTCEPSS rescore
  6. 2026-06-30 23:19 UTCEPSS rescore
  7. 2026-06-28 14:03 UTCEPSS rescore
  8. 2026-06-27 03:05 UTCEPSS rescore
  9. 2026-06-25 13:46 UTCEPSS rescore
  10. 2026-06-24 14:02 UTCEPSS rescore
  11. 2026-06-24 14:02 UTCEPSS rescore
  12. 2026-06-23 21:30 UTCEPSS rescore
  13. 2026-06-23 21:29 UTCEPSS rescore
  14. 2026-06-21 14:53 UTCEPSS rescore
  15. 2026-06-18 17:49 UTCEPSS rescore
  16. 2026-06-18 17:49 UTCEPSS rescore
  17. 2026-06-17 17:49 UTCEPSS rescore
  18. 2026-06-17 17:49 UTCEPSS rescore
  19. 2026-06-15 17:44 UTCEPSS rescore
  20. 2026-06-12 23:08 UTCEPSS rescore
  21. 2026-06-12 23:08 UTCEPSS rescore
  22. 2026-06-10 22:14 UTCEPSS rescore
  23. 2026-06-08 14:13 UTCEPSS rescore
  24. 2026-06-07 15:22 UTCEPSS rescore
  25. 2026-06-07 15:22 UTCEPSS rescore
  26. 2026-06-04 13:09 UTCEPSS rescore
  27. 2026-06-04 13:09 UTCEPSS rescore
  28. 2026-05-31 00:14 UTCEPSS rescore
  29. 2026-05-31 00:13 UTCEPSS rescore
  30. 2026-05-29 12:11 UTCEG score recompute
  31. 2026-05-29 12:11 UTCVendor advisory
  32. 2026-05-29 12:11 UTCGHSA enrichment
  33. 2026-05-27 13:38 UTCEPSS rescore
  34. 2026-05-27 13:38 UTCEPSS rescore
  35. 2026-05-26 13:41 UTCEPSS rescore
  36. 2026-05-26 13:41 UTCEPSS rescore
  37. 2026-05-24 16:43 UTCEPSS rescore
  38. 2026-05-22 21:15 UTCEPSS rescore
  39. 2026-05-22 21:15 UTCEPSS rescore
  40. 2026-05-22 21:15 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

(7 references)

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

  • GitHub PoComarothmann/Embedded-Backdoor-Connection
    First seen Jan 26, 2022

    This demonstration video shows how we can control the victim's device by sending the innocent-looking PDF file to the target which actually consists of embedded payload. The exploit was made public as CVE-2010-1240.

    Open source ↗
  • GitHub PoCJasmoon99/Embedded-PDF
    First seen Jun 5, 2021

    This demonstration video shows how we can control the victim's device by sending the innocent-looking PDF file to the target which actually consists of embedded payload. The exploit was made public as CVE-2010-1240.

    Open source ↗
  • Exploit-DBEDB-16671✓ verified
    First seen Dec 16, 2010

    Adobe PDF - Embedded EXE Social Engineering (Metasploit)

    Open source ↗
  • Exploit-DBEDB-16682✓ verified
    First seen Dec 16, 2010

    Adobe PDF - Escape EXE Social Engineering (No JavaScript) (Metasploit)

    Open source ↗
  • Exploit-DBEDB-11987✓ verified
    First seen Mar 31, 2010

    Adobe Reader - Escape From '.PDF' Execute Embedded Executable

    Open source ↗
  • Metasploitexploit/windows/fileformat/adobe_pdf_embedded_exe✓ verified
    First seen Mar 29, 2010

    Adobe PDF Embedded EXE Social Engineering

    Open source ↗
  • Metasploitexploit/windows/fileformat/adobe_pdf_embedded_exe_nojs✓ verified
    First seen Mar 29, 2010

    Adobe PDF Escape EXE Social Engineering (No JavaScript)

    Open source ↗

Frequently asked(4)

What is CVE-2010-1240?
CVE-2010-1240 is a high vulnerability published on April 5, 2010. Adobe Reader and Acrobat 9.x before 9.3.3, and 8.x before 8.2.3 on Windows and Mac OS X, do not restrict the contents of one text field in the Launch File warning dialog, which makes it easier for remote attackers to trick users into executing an arbitrary local program that was specified in a PDF…
When was CVE-2010-1240 disclosed?
CVE-2010-1240 was first published in the National Vulnerability Database on April 5, 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-1240 actively exploited?
CVE-2010-1240 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 74% probability of exploitation in the next 30 days, which ranks it in the top 0.6% of all scored CVEs.
How do I remediate CVE-2010-1240?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2010-1240, 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-1240

Explore →

Is Your Infrastructure Affected by CVE-2010-1240?

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

Start Free Scan →Browse All CVEs