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

Adobe Acrobat and Reader vulnerability

Adobe Acrobat and Reader contain a stack-based buffer overflow (CWE-119) allowing remote code execution or denial-of-service. This vulnerability has been exploited in the wild with high EPSS score of 0.928.

Verdict

Today item — known-exploited.

A remotely exploitable memory corruption flaw in widely deployed PDF software enables attackers to achieve arbitrary code execution on victim systems without user interaction beyond opening a malicious document. Active exploitation in the wild confirms practical weaponization.

CISA KEV Yes · 2022-06-083EPSS 0.82485 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
14 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 2022-06-08).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.82485 — 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 document containing specially crafted data that overflows a stack buffer in the PDF parser.
Business
Attackers gain a reliable delivery mechanism for code execution targeting millions of Acrobat and Reader users globally.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I distribute the malicious PDF via email, web hosting, or watering hole attacks to reach target victims.
Business
Organizations face compromise of employee systems and potential lateral movement into corporate networks through a ubiquitous application.
3

Lateral reach — past segmentation narrative 3

Attacker
I execute arbitrary code with the privileges of the user running the vulnerable application.
Business
Attackers establish persistent access, steal sensitive data, deploy malware, or pivot to critical infrastructure within affected organizations.
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)
  • 14 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.