CVE Intelligence
Skip to main content
CISA KEVhighRemote Code Execpublic exploit

CVE-2009-3459

Adobe Acrobat and Reader Heap-Based Buffer Overflow Vulnerability

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.

Published Updated Sources: NVD, Adobe (CNA), CISA, FIRST EPSS, GitHub, GitHub Security Advisory, Exploit-DB

Triage

Is it exploited, how likely is exploitation, what does it touch, and how severe do the scoring sources call it.

Exploitation

Confirmed

CISA KEV, listed May 20, 2026

EPSS

87%

ahead of 99.7% of scored CVEs

Affects

Adobe

Acrobat and Reader

CVSS base

9.3

high · 2 sources

CISA SSVC assessment

Three decision points CISA publishes for the CVEs it assesses · SSVC 2.0.3. A stakeholder decision, not a severity score.

CISA

Exploitation

Active

none · proof-of-concept · active

Automatable

No

can an attacker script all four kill-chain steps

Technical impact

Total

partial · total control of the vulnerable component

Remediation

The vendor's own words where we have them.

Upgrade Acrobat and Reader to a fixed release. Apply vendor patches per advisory and restrict external exposure of the affected component until patched.

CISA 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.

Federal deadline Jun 3, 2026 — passed 81 days ago

First 24 hours

Ordered from the record's own fields — exposure first, because you cannot patch what you have not found.

  • Identify exposed assets running affected vendor/product/version combinations.
  • Treat as emergency remediation because CISA KEV status is present.
  • Search available logs for exploit probes, errors, authentication anomalies, or suspicious child processes matching the vulnerability class.

Affected scope

Vendor, product and version as the advisories word them.

VendorProductVersionsStatus
AdobeAcrobat and ReaderVulnerable

Attack characteristics

The CVSS vector, decoded. It describes the attack, not your exposure to it.

Availability

Changed

Confidentiality

Changed

Integrity

Changed

Attack Complexity

M

Attack Vector

Network

Every base score collected

Sources score independently and disagree; each row says who scored it and under which version.

ScoreVersionSeverityExpl.ImpactSource
8.8CVSS 3.1high2.85.9CNA, GHSA
9.3CVSS 2.0high8.610NVD

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Weakness & attack patterns

  • CWE-119
  • CWE-122

Inferred from the weakness class — not observed against this CVE.

CAPEC-242 · Code InjectionCAPEC-35 · Leverage Executable Code in Non-Executable Files

CISA KEV details

CISA lists a CVE here once it has evidence of exploitation against real targets.

Listed

May 20, 2026

Federal deadline

Jun 3, 2026

passed 81 days ago

Ransomware use

Unknown

CISA records ransomware use only for campaigns it has confirmed, so “Unknown” means unrecorded, not ruled out. The deadline binds US federal agencies; for everyone else it is a date to argue against.

Public exploit

Capability, not use: code existing is a different claim from anyone running it.

Repositories

6

Exploit entries

2

Exploit-DB and CTI exploit indexes

Detection

Read off the CVSS vector and the weakness class. Starting points, not rules we have tested.

  • Prioritize edge telemetry for network-reachable Acrobat and Reader.
  • Monitor for scanner or exploit-pattern traffic after 8 public PoC repositories were reported.
web/proxy/WAF logsapplication logsnetwork IDS/IPSEDR process telemetryhost service logs

Timeline

What happened to this CVE, newest first — with the readings a source repeats on a schedule counted underneath rather than listed.

  1. 2026
  2. Added · CVSS 3.1 9.3 (AV:N)

    Jun 16, 2026 · NVD

  3. Added to CISA KEV catalog

    May 20, 2026 · CISA

  4. 2022
  5. Added · GHSA-q52p-3m33-w676 published (high)

    May 2, 2022 · GitHub Security Advisory

  6. 2010
  7. Added · Verified local entry: Adobe - FlateDecode Stream Predictor 02 Integer Overflow (Metasploit) (2)

    Sep 25, 2010 · Exploit-DB

  8. Added · Verified local entry: Adobe - FlateDecode Stream Predictor 02 Integer Overflow (Metasploit) (1)

    Sep 20, 2010 · Exploit-DB

  9. 2009
  10. Initial · CVE published

    Oct 13, 2009 · NVD

References

19 on the record

Elsewhere on this site

Not in any source we poll

Listed rather than left blank: an empty field and an unmeasured one look identical on screen, and only one is a reason to look elsewhere.

  • No confirmed IOCs, IP addresses, domains, file hashes, or malware artifacts supplied.
  • No organization-specific asset inventory, compensating-control status, or patch deployment evidence supplied.
  • No exploit packet captures, log samples, or incident case IDs supplied.
Answered from this record1

What should defenders know first?

CVE-2009-3459 is Adobe Acrobat and Reader Heap-Based Buffer Overflow Vulnerability, a high vulnerability affecting Acrobat and Reader from Adobe. The current evidence lists it in CISA KEV, and the exploit status is: Yes: CISA KEV signal present. Public exploit evidence is: 8 public PoC repositories reported; 0 marked weaponized in current dataset. The affected-version evidence is listed in the key facts and affected products tables. Defenders should first verify whether exposed or business-critical assets run those versions, then apply vendor patches or mitigations, restrict reachable attack surface, and preserve logs for detection review. CVSS 9.3 describes technical severity, while EPSS 87% helps estimate near-term exploit likelihood; neither replaces asset context. Unknown fields should remain explicit in tickets, and threat actor, IOC, victimology, or payload claims should not be added unless a cited source supports them. Monitor CISA KEV, vendor advisories, NVD changes, public PoC repositories, and internal telemetry for update triggers.