Adobe Acrobat and Reader Heap-Based Buffer Overflow
CVE-2009-3459 is a high-severity improper restriction of operations within the bounds of a memory buffer vulnerability in Acrobat from Adobe, with a CVSS 2.0 base score of 9.3 out of 10. It can be exploited remotely over the network by an unauthenticated attacker, without any action from a user. The record lists versions 7.1.4, 8.1.7, 9.2 as the first without the flaw, so updating Acrobat to one of those releases or later removes the exposure. CISA added it to the Known Exploited Vulnerabilities catalogue on May 20, 2026, which means attacks have been observed in the wild.
Attackers are already exploiting this vulnerability, according to CISA.
What to do
- Update Acrobat to 7.1.4 or 8.1.7 or 9.2, whichever matches your release line, or a later version.
- Update Acrobat Reader to 7.1.4 or 8.1.7 or 9.2, whichever matches your release line, or a later version.
- CISA's required action: Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.
- Read the advisory on secunia.com for workarounds and exact fixed builds.
- Until you can update, restrict network access to the affected service so it is not reachable from untrusted networks.
Affected products and versions
| Vendor | Product | Affected versions | Fixed in |
|---|---|---|---|
| Adobe | Acrobat | 7.0 up to, but not including, 7.1.4; 8.0 up to, but not including, 8.1.7; 9.0 up to, but not including, 9.2 | 7.1.4, 8.1.7, 9.2 |
| Adobe | Acrobat Reader | 7.0 up to, but not including, 7.1.4; 8.0 up to, but not including, 8.1.7; 9.0 up to, but not including, 9.2 | 7.1.4, 8.1.7, 9.2 |
Version data comes from NVD's product matching. Confirm against the vendor advisory before deciding you are unaffected.
How the severity score breaks down
- Access vector
- NetworkCan be exploited remotely over a network.
- Access complexity
- MediumSome conditions must be met.
- Authentication
- NoneNo login is needed.
- Confidentiality
- CompleteAll data can be read.
- Integrity
- CompleteAny data can be modified.
- Availability
- CompleteThe system can be shut down completely.
Vector: AV:N/AC:M/Au:N/C:C/I:C/A:C. Scored by NVD.
| Scoring system | Score | Severity | Scored by |
|---|---|---|---|
| CVSS 3.1 | 8.8 | High | CISA (ADP) |
| CVSS 2.0 | 9.3 | High | NVD |
Official description
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.
Source: the CVE record as published by its numbering authority, via NVD and CVE.org.
The underlying weakness: Improper Restriction of Operations within the Bounds of a Memory Buffer
The product performs operations on a memory buffer, but it reads from or writes to a memory location outside the buffer's intended boundary.
How developers prevent this class of flaw
- Use a language that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. For example, many languages that perform their own memory management, such as Java and Perl, are not subject to buffer overflows. Other languages, such as Ada and C#, typically provide overflow protection, but the protection can be disabled by the programmer. Be wary that a language's interface to native code may still be subject to overflows, even if the language itself is theoretically safe.
- Use a vetted library or framework that does not allow this weakness to occur or provides constructs that make this weakness easier to avoid. Examples include the Safe C String Library (SafeStr) by Messier and Viega, and the Strsafe.h library from Microsoft. These libraries provide safer versions of overflow-prone string-handling functions.
- Use automatic buffer overflow detection mechanisms that are offered by certain compilers or compiler extensions. Examples include: the Microsoft Visual Studio /GS flag, Fedora/Red Hat FORTIFY_SOURCE GCC flag, StackGuard, and ProPolice, which provide various mechanisms including canary-based detection and range/index checking. D3-SFCV (Stack Frame Canary Validation) from D3FEND discusses canary-based detection in detail.
Timeline
- CVE record published.
- CISA published its SSVC assessment (exploitation: active, automatable: no, technical impact: total).
- Added to CISA's Known Exploited Vulnerabilities catalogue.
- Deadline for US federal agencies to remediate, set by CISA.
- Record last changed materially (score, affected products, status or references).
References
Advisories
Third-party and government advisories
- us-cert.gov/cas/techalerts/TA09-286B.htmlUS Government Resource
- exchange.xforce.ibmcloud.com/vulnerabilities/53691Third Party Advisory, VDB Entry
- cisa.gov/known-exploited-vulnerabilities-catalog?field_cve=CVE-2009-3459US Government Resource
Other references
- isc.sans.org/diary.html?storyid=7300Not Applicable
Other vulnerabilities in Acrobat
- 8.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
- 7.8 High severity
Recent Improper Restriction of Operations within the Bounds of a Memory Buffer vulnerabilities
- 9.3 High severity
Spotted an error? Tell us.