basicsecurity.net
Proof, not just disclosure.
Threats / Adobe / CVE-2009-3459
CVE-2009-3459 · EUVD no mirror located · GCVE no mirror located Verified 2026-06-22

Adobe Acrobat and Reader vulnerability

Adobe Acrobat and Reader contain a heap-based buffer overflow in PDF processing that allows remote code execution when opening a malicious PDF file.

Verdict

Today item — known-exploited.

A remote attacker can craft a PDF document that triggers memory corruption in Adobe Acrobat or Reader, leading to arbitrary code execution on the victim's system. This vulnerability has been actively exploited in the wild.

CISA KEV Yes · 2026-05-203EPSS 0.86468 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
3 independent public reports of in-the-wild exploitation are cataloged.Distinct reporting sources (vendor, incident response, government); open them for the underlying claims.
Exploited in the wild
Listed in the CISA Known Exploited Vulnerabilities catalog (added 2026-05-20).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.86468 — modeled likelihood of exploitation activity.EPSS is a daily-changing model output — open the source for today's value.
Severity / affected
Affected: Adobe, Acrobat and Reader. Confirm exact fixed builds in the vendor advisory.
NVD ↗Reported
Weakness (CWE)
Mapped to CWE-119 Memory Buffer Bounds Error — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
02

Who’s exploiting it?

— attribution turns risk into urgency
Attribution not established

No confirmed (advisory-backed) threat-actor attribution is established for this record. Absence of a named actor is not absence of compromise — see Coverage & confidence.

03

Why it matters

— the attack path, told twice: adversary, then board
1

Front door — unauthenticated access narrative 1

Attacker
I craft a malicious PDF file designed to overflow a heap buffer during parsing.
Business
An employee receives the PDF via email or downloads it from a compromised website.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the PDF to the target through email, web download, or file sharing.
Business
The organization's email and web security controls fail to detect the malicious payload.
3

Lateral reach — past segmentation narrative 3

Attacker
I trigger code execution when the victim opens the PDF in Acrobat or Reader.
Business
Arbitrary code runs with the privileges of the user who opened the file.
4

Data at risk — exfiltration narrative 4

Attacker
I establish persistence and move laterally within the network.
Business
Sensitive data is accessed, exfiltrated, or systems are compromised for further attacks.
04

What to do

— defensible action
  • Remediate per the vendor advisory — confirm the fixed build for your version and verify exposure.1
Say it to the boardA vulnerability with this evidence profile is a defensible budget line, not a backlog ticket — fund the change against the proof above.
05

Coverage & confidence

— what we know, and what we don’t

Established (cited)

  • KEV listing (CISA)
  • EPSS probability (FIRST)
  • 3 reported-exploitation source(s)
  • CWE weakness mapping (NVD)
  • Catalogued by adobe (CNA)
  • Coverage gaps — stated, not hidden

  • No EUVD / GCVE mirror in feed — single-authority dependency for the identifier.
  • EPSS & exposure are time-varying; verify live at the source.
  • Threat-actor attribution not established from feed data — absence of a name is not absence of compromise.
  • No finder/reporter credit recorded in the public CVE entry — the work behind this find is unattributed.
  • Disclosure & credit2
    Catalogued by adobeCNA
    Credited with finding itNo finder named in the public CVE record — the work behind this find is unattributed.