Buffer overflow in Adobe Reader 9.0 and earlier, and Acrobat 9.0 and earlier, allows remote attackers to execute arbitrary code via a crafted PDF document, related to a non-JavaScript function call and possibly an embedded JBIG2 image stream, as exploited in the wild in February 2009 by Trojan.Pidief.E.
CVE-2009-0658
“▲” beside the score: it is higher than NVD's CVSS score.
Score elevated to 9.0 because EPSS predicted 88% probability of exploitation within the next 30 days (99th percentile of EPSS-scored CVEs) when EchelonGraph scored this CVE. NVD baseline CVSS 7.8 retained for reference. Confidence: see factors.
- High exploitation likelihood — EPSS 88%
- Public exploit code is available (Metasploit, Exploit-DB, marked verified by Exploit-DB)
A fix is available — apply it.
- CVSS v3
- 7.8
- EG Score
- 9.0CRITICALhigh confidence
- EG Risk
- 76EG Risk 76/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.Exploitation88% × 40%FIRST EPSS: the 30-day exploitation probability when EchelonGraph scored this CVE.Automatability0% × 15%CISA's BOD 26-04 default: no one has published Automatable for this CVE, and CISA treats it as “no” for a CVE not in KEV.SSVC (CISA's decision table, applied by EchelonGraph): Track at low, Track* at medium and Attend at high mission impact.Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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 available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high. - EPSS PROB
- 88%
- EPSS %ILE
- 99th
- KEV
- Not listed
SSVC (CISA's decision table, applied by EchelonGraph)Track at low, Track* at medium and Attend at high mission impact.
A fix is available. Apply it within your standard update timelines at low or medium mission impact and sooner than that at high.
Exploitation public PoC (exploit code on record) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). EchelonGraph holds no SSVC assessment of this CVE from CISA: none of these inputs is from 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)14 days if the affected system is publicly exposed; Fix on system upgrade if it is not.
In CISA KEV no (CISA's KEV catalog) · Automatable no (CISA's BOD 26-04 default) · Technical impact total (CISA's BOD 26-04 default). Where an input reads “CISA's BOD 26-04 default”, no one has published it for this CVE, and CISA's implementation guidance says: “If “Automatable” and “Technical Impact” information items about a CVE ID are not available and the CVE ID is not in the KEV Catalog, CISA will treat its values as “no” and “total,” respectively, until CISA or a third party provides metadata about the CVE ID. CISA will always provide the Vulnrichment data for a CVE ID listed in the KEV Catalog.” 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
Published
February 20, 2009
Last Modified
April 23, 2026
Advisory Details (7)
Auto-updated May 30, 2026Adobe Reader: User-assisted execution of arbitrary code (GLSA 200904-17) — Gentoo security
http://security.gentoo.org/glsa/glsa-200904-17.xmlSANS.edu Internet Storm Center - SANS Internet Storm Center
http://isc.sans.org/diary.html?n&storyid=5902Patch Availability(1)
| Vendor / Ecosystem | Fix (by version range) / Patch | Released | Source |
|---|---|---|---|
| redhat | acroread-0:8.1.4-1.el5 | 2009-03-25 | redhat |
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.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
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 3× in last 7d / 12× 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.
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. 10 repeat rows among the latest 53 are merged into the row they repeat.
- 2026-10-12 01:55 UTCEG score recompute
- 2026-10-07 23:37 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-06 15:09 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-10-04 23:15 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-30 14:58 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-29 07:57 UTCEG score recompute
- 2026-09-26 15:52 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-24 13:57 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-17 19:20 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-15 03:04 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-13 16:40 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-12 14:54 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-10 09:24 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-06 13:41 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-09-05 15:22 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-08-28 21:34 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-08-06 13:41 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-08-03 10:28 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-25 14:12 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-24 14:12 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-23 14:14 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-23 00:58 UTCEG score recompute
- 2026-07-23 00:36 UTCEG score recompute
- 2026-07-23 00:03 UTCEG score recompute
- 2026-07-22 21:42 UTCEG score recompute
Show 18 moreShow fewer
- 2026-07-22 14:03 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-15 16:54 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-15 01:55 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-13 06:07 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-05 02:26 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-07-01 15:02 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-06-25 13:46 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-06-23 21:29 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-06-17 17:49 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-06-15 17:44 UTCEPSS rescoreEPSS 88% · 99th percentile
- 2026-06-12 23:08 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-06-01 13:49 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-31 00:13 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-30 18:06 UTCEG score recompute
- 2026-05-30 18:06 UTCVendor advisory
- 2026-05-30 18:06 UTCGHSA enrichmentGHSA-pm5j-jrq9-vmhx · GitHub severity HIGH · GitHub CVSS 7.8
- 2026-05-28 13:42 UTCEPSS rescoreEPSS 92% · 99th percentile
- 2026-05-18 21:29 UTCEPSS rescoreEPSS 92% · 99th percentile
Publicly available exploits
(5 references)Public exploit code is referenced for this CVE (2 Metasploit modules, 3 Exploit-DB entries). Defenders should treat patch urgency accordingly.
- Exploit-DBEDB-16672✓ verifiedPublished Sep 25, 2010
Adobe - JBIG2Decode Memory Corruption (Metasploit) (2)
Open source ↗ - Exploit-DBEDB-16593✓ verifiedPublished Jun 15, 2010
Adobe - JBIG2Decode Memory Corruption (Metasploit) (1)
Open source ↗ - Metasploitexploit/windows/browser/adobe_jbig2decode✓ verifiedPublished Mar 31, 2009
Adobe JBIG2Decode Heap Corruption
Open source ↗ - Metasploitexploit/windows/fileformat/adobe_jbig2decode✓ verifiedPublished Mar 27, 2009
Adobe JBIG2Decode Memory Corruption
Open source ↗ - Exploit-DBEDB-8099✓ verifiedPublished Feb 23, 2009
Adobe Acrobat Reader - JBIG2 Local Buffer Overflow (PoC) (2)
Open source ↗
Related CVEs(same vendor + same CWE)
Same vendor
4 shownredhat:RHSA-2009:0376
Same CWE
10 shownCWE-119
Frequently asked(5)
What is CVE-2009-0658?
When was CVE-2009-0658 made public?
Is CVE-2009-0658 actively exploited?
What is the CVSS score of CVE-2009-0658?
How do I remediate CVE-2009-0658?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2009-0658
Is Your Infrastructure Affected by CVE-2009-0658?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.