CVE-2009-3459
Adobe Acrobat and Reader Heap-Based Buffer Overflow Vulnerability
Adobe Acrobat and Reader
Heap-based buffer overflow in Adobe Reader and Acrobat 7.x before 7.1.4, 8.x before 8.1.7, and 9.x before 9.2 allows remote attackers to execute arbitrary code via a crafted PDF file that triggers memory corruption, as exploited in the wild in October 2009. NOTE: some of these details are obtained from third party information.
Exploitation status
CISA Known Exploited Vulnerabilities
Listed by CISA on 20 May 2026. US federal agencies were required to remediate it by 3 June 2026.
EPSS — exploitation probability
FIRST puts the probability of exploitation activity in the next 30 days at 86.6%, which is higher than 99.7% of all scored vulnerabilities. EPSS is a forecast of activity, not a measure of severity, and it is rescored daily.
CVSS vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Frequently asked questions
Is CVE-2009-3459 being exploited by ransomware groups?
No ransomware group in this database is currently recorded as exploiting CVE-2009-3459.
What does CVE-2009-3459 affect?
CVE-2009-3459 affects Adobe Acrobat and Reader. Heap-based buffer overflow in Adobe Reader and Acrobat 7.x before 7.1.4, 8.x before 8.1.7, and 9.x before 9.2 allows remote attackers to execute arbitrary code via a crafted PDF file that triggers memory corruption, as exploited in the wild in October 2009. NOTE: some of these details are obtained from third party information.
How severe is CVE-2009-3459?
CVE-2009-3459 is rated HIGH with a CVSS base score of 8.8. EPSS puts the probability of exploitation in the next 30 days at 86.6%, higher than 99.7% of all scored vulnerabilities. It is listed in the CISA Known Exploited Vulnerabilities catalog, with a federal remediation deadline of 3 June 2026.
How should organisations respond to CVE-2009-3459?
Apply the vendor patch for Adobe Acrobat and Reader as the first priority, and treat any internet-facing instance as the most urgent. Because this vulnerability is associated with ransomware activity, also review whether the affected systems were reachable before patching, rather than assuming that patching alone closes the incident.