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

Adobe Acrobat and Reader vulnerability

Adobe Acrobat and Reader contain an out-of-bounds write vulnerability (CWE-787) enabling arbitrary code execution. The flaw has been exploited in the wild.

Verdict

Today item — known-exploited.

Out-of-bounds write in Adobe's PDF readers allows attackers to execute code by crafting malicious documents. Active exploitation in the wild confirms practical weaponization of this memory corruption defect.

CISA KEV Yes · 2023-09-143EPSS 0.07036 (verify live)4
01

Is it exploitable?

— the evidence, ranked above the score
Reported exploitation
6 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 2023-09-14).
CISA KEV ↗Confirmed
Probability (EPSS)
EPSS 0.07036 — 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-787 Out-of-bounds Write — weakness family: Memory safety.CWE assignment from the public NVD record; the weakness class drives how the flaw is exploited.
NVD ↗Reported
WeaknessCWE-787 · Out-of-bounds WriteMemory safety
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 data that triggers an out-of-bounds write when processed by the vulnerable reader.
Business
Users opening untrusted PDF files face immediate risk of system compromise and data theft.
2

Keys to the kingdom — privilege/identity takeover narrative 2

Attacker
I deliver the malicious PDF via email, web download, or document sharing to reach target systems running unpatched Acrobat or Reader.
Business
Enterprise email and web security controls may fail to detect PDF-based code execution payloads, enabling breach of corporate networks.
3

Lateral reach — past segmentation narrative 3

Attacker
Upon opening the document, the out-of-bounds write corrupts memory and executes my injected code with the privileges of the reader process.
Business
Attackers gain initial access to systems, potentially leading to lateral movement, data exfiltration, or persistent compromise.
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)
  • 6 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.