CVE-2009-3459Adobe Acrobat and Reader Heap-Based Buffer Overflow Vulnerability

Patch nowHigh8.8ExploitedEPSS 87%

CVE-2009-3459 is a heap-based buffer overflow in Adobe Acrobat and Reader, rated high (8.8 on CVSS 3.1).

Why this priority: Exploited in the wild: listed in CISA's KEV catalog.

Published 13 Oct 2009 · Updated 16 Jun 2026 · NVD status: Analyzed

What it is

A buffer on the heap overflows and corrupts neighbouring data structures. Code reads or writes outside the memory it was given, which can corrupt the process.

How it is reached

An attacker can exploit it over the network, without an account, but someone has to act first, such as opening a file or following a link.

What an attacker gains

A successful attack can read the data it protects, change data or behaviour and take it offline. In practice, this kind of flaw lets an attacker crash the process, read memory, or in the worst case run code.

Is it being exploited?

CISA added it to the Known Exploited Vulnerabilities catalog on 2026-05-20: it is being exploited in the wild. EPSS estimates a 87% chance of exploitation activity in the next 30 days, higher than 100% of scored CVEs.

What to do

Treat it as urgent: it is on CISA's KEV list. CISA's deadline for US federal agencies: 2026-06-03.
Apply the update for your edition of Adobe Acrobat and Reader. Fixed builds: Acrobat: 7.1.4, 8.1.7, 9.2; Acrobat Reader: 7.1.4, 8.1.7, 9.2. The patch notes are linked below.
Until it is patched, keep it off the internet or behind a VPN, allowlist or authenticating proxy.
Warn the people who use it, and filter files and links on the way in.
Check exposed instances for signs of compromise, not only for the version.

Description from NVD

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.

What this means for your architecture.

A CVE names a product. Whether it matters depends on where that product sits in your systems: what reaches it, which trust boundary it guards and what it can reach once compromised. Veriom maps your components, their relationships and your trust boundaries from your code, cloud and delivery evidence, so you can see where a component like this sits. The radar itself does not look at your systems.

Components it touches

Native code: operating systems, browsers and firmware. The flaw sits wherever native code reads untrusted data.
Network appliances and media or file parsers. The flaw sits wherever native code reads untrusted data.

Trust boundaries in play

Internet-facing entry points. No account is needed. Any instance reachable from outside your perimeter, through a load balancer, gateway, VPN or exposed admin port, is in scope.
People who open files and links. Mail, chat and browsers are the delivery path.
Wherever native code reads untrusted data. An attacker who crosses it can crash the process, read memory, or in the worst case run code.

Questions to answer about your own systems

Where does Adobe Acrobat and Reader run in your systems, and at which version?
Which of those instances can be reached from the internet or partner networks?
What can it reach once compromised: which data stores, secrets and services?

See how Veriom maps an architecture Take the interactive tour

Patches and commits

www.adobe.com/support/security/bulletins/apsb09-15.html

Advisories

Sources

CVE records and CVSS scores from the NVD CVE API. This product uses the NVD API but is not endorsed or certified by the NVD.
Exploitation status from CISA’s Known Exploited Vulnerabilities catalog.
Exploit likelihood from FIRST’s Exploit Prediction Scoring System (EPSS), refreshed daily.
Explanations are written by Veriom from fixed templates over each record’s data, not by a person reviewing each CVE. Descriptions are quoted from the records as published.