CVE-2009-3459
KEVAdobe Acrobat and Reader Heap-Based Buffer Overflow Vulnerability
Description
Adobe Acrobat and Reader contain a heap-based buffer overflow vulnerability which could allow remote attackers to execute arbitrary code via a crafted PDF file that triggers memory corruption.
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.
CVSS 3.1 vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HPublishedOct 13, 2009
Last modifiedJun 16, 2026
Added to KEVMay 20, 2026
Remediation dueJun 3, 2026
References
- blogs.adobe.com/psirt/2009/10/adobe_reader_and_acrobat_issue_1.htmlBroken LinkVendor Advisory
- isc.sans.org/diary.html?storyid=7300Not Applicable
- secunia.com/advisories/36983Vendor Advisory
- securitytracker.com/id?1023007Broken Link
- adobe.com/support/security/bulletins/apsb09-15.htmlPatchVendor Advisory
- iss.net/threats/348.htmlBroken Link
- securityfocus.com/bid/36600Broken Link
- us-cert.gov/cas/techalerts/TA09-286B.htmlUS Government Resource
- vupen.com/english/advisories/2009/2851Vendor Advisory
- vupen.com/english/advisories/2009/2898Vendor Advisory
- exchange.xforce.ibmcloud.com/vulnerabilities/53691Third Party AdvisoryVDB Entry
- oval.cisecurity.org/repository/search/definition/oval%3Aorg.mitre.oval%3Adef%3A6534Broken Link
0 recent articles mention this CVE
83
Risk assessment · Critical
Actively exploited. Patch immediately.
- Exploitation
- Confirmed in the wild (CISA KEV)
- Federal remediation deadline
- Overdue by 145 days
- CVSS
- 8.8 HIGH
- EPSS (30-day exploit probability)
- 86.6% · top 1% of all CVEs
- Weakness
- CWE-119
- Attack vector
- Network, remotely reachable
Recommended actions
- 1.Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- 2.Treat as emergency change: patch or isolate internet-facing instances first.
- 3.Review exposure: confirm which instances are reachable from the internet and restrict access until patched.
- 4.Hunt for compromise: review logs for the disclosure window, not just from the patch date.
Assessment is derived automatically from the live signals above; verify against your own asset inventory.