CVE Intelligence
CISA KEV High Memory corruption exploit reference

CVE-2020-9715 — Adobe Acrobat Use-After-Free Vulnerability

Adobe Acrobat and Reader versions 2020.009.20074 and earlier, 2020.001.30002, 2017.011.30171 and earlier, and 2015.006.30523 and earlier have an use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution .

Published Aug 19, 2020 · Updated Oct 13, 2026 · Sources: CISA Known Exploited Vulnerabilities, CVE Program (cve.org) e CISA ADP, NIST National Vulnerability Database, GitHub Security Advisories · CNA: adobe

Who exploits it and how urgent it is

A 0–100 score combining confirmed exploitation, ransomware and APT use, public exploits, EPSS and severity.

CISA KEV · Apr 13, 2026
How the score was calculated
  • Confirmed exploitation (CISA KEV)+35
  • EPSS 48.6% (30-day exploitation probability)+15
  • Technical severity (high)+6

The score orders the patch queue; it does not replace your asset context (internet exposure, criticality, compensating controls).

Triage

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

Exploitation
Confirmed
CISA KEV, listed Apr 13, 2026
EPSS FIRST
48.6%
ahead of 99% of scored CVEs · Oct 14, 2026
Affects
Adobe
Acrobat DC and 2 more
CVSS base
7.8
High · 4 source(s)

CISA SSVC assessment CISA

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

Exploitation
Active
none · proof-of-concept · active
Automatable
No
can an attacker script the kill-chain steps
Technical impact
Total
partial · total control of the vulnerable component

Remediation

Fixes and mitigations documented by the sources — linked to the original advisory.

CISA required action CISA

Apply mitigations per vendor instructions, follow applicable BOD 22-01 guidance for cloud services, or discontinue use of the product if mitigations are unavailable.

US federal deadline: Apr 27, 2026 — passed 171 day(s) ago

First 24 hours

Ordered from the record’s own fields — exposure first, because you cannot patch what you have not found. A rule-generated starting point.

  1. Identify exposed assets running the affected vendor/product/version combinations (Adobe Acrobat DC, Adobe Acrobat Reader DC, Adobe Adobe Acrobat and Reader).
  2. Treat as emergency remediation: the CVE is in CISA KEV (confirmed exploitation).
  3. Apply the fixed version or the patch documented under Remediation.
  4. Exploitation requires user interaction: tighten email/web filtering and warn affected users.
  5. EPSS ahead of 99% of scored CVEs: prioritize it in the patch queue.
  6. Search available logs for exploit probes matching the vulnerability class (memory corruption), errors and authentication anomalies.

Affected scope

Vendor, product and versions as the sources word them.

VendorProductVersionsStatusSource
Adobe Acrobat DC ≥ 15.006.30060 and ≤ 15.006.30523≥ 15.008.20082 and ≤ 20.009.20074≥ 17.011.30059 and ≤ 17.011.30171version 20.001.30002 Vulnerable NIST National Vulnerability Database
Adobe Acrobat Reader DC ≥ 15.006.30060 and ≤ 15.006.30523≥ 15.008.20082 and ≤ 20.009.20074≥ 17.011.30059 and ≤ 17.011.30171version 20.001.30002 Vulnerable NIST National Vulnerability Database
Adobe Adobe Acrobat and Reader version 2020.009.20074 and earlier, 2020.001.30002, 2017.011.30171 and earlier, and 2015 Vulnerable CVE Program (cve.org) e CISA ADP

Attack characteristics

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

Attack vector
Local
Attack complexity
Low
Privileges required
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

Every base score collected

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

ScoreVersionSeverityExpl.ImpactScored by
7.8 CVSS 3.1 High 1.8 5.9 nvd@nist.gov via NIST National Vulnerability Database
7.8 CVSS 3.1 High 1.8 5.9 134c704f-9b21-4f2e-91b3-4a467353bcc0 via NIST National Vulnerability Database
7.8 CVSS 3.1 High — — GitHub, Inc. via GitHub Security Advisories
7.8 CVSS 3.1 High — — CISA-ADP via CVE Program (cve.org) e CISA ADP
9.3 CVSS 2.0 High 8.6 10.0 nvd@nist.gov via NIST National Vulnerability Database
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H (score shown at the top: nvd@nist.gov)

Weakness MITRE

Weakness class according to MITRE’s CWE catalog.

CWE-416 · Use After Free

Other CVEs with this weakness →

CISA KEV details CISA

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

Listed
Apr 13, 2026
Federal deadline
Apr 27, 2026
passed 171 day(s) 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 reference date.

EPSS over time FIRST

Oct 12, 2026 → Oct 14, 2026 · 3 reading(s) · max 48.60%

Detection

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

  • Local/physical vector: focus on endpoint telemetry (EDR) from affected hosts.
  • Correlate service crashes/restarts with inbound traffic; repeated crashes may indicate attempts.
  • Hunt retroactively in logs from before Apr 13, 2026 (KEV listing): exploitation may have started earlier.
endpoint telemetry (EDR)crash dumps

Timeline

What happened to this CVE, newest first.

  • 2026
  • Fix documented
    Oct 13, 2026 · NIST National Vulnerability Database
  • Affected products added · adobe/acrobat dc, adobe/acrobat reader dc
    Oct 13, 2026 · NIST National Vulnerability Database
  • Source status changed · Published → Analyzed
    Oct 13, 2026 · NIST National Vulnerability Database
  • Record published
    Oct 13, 2026
  • Affected products added · adobe/adobe acrobat and reader
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • CVSS changed · 7.8
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Source status changed · → Published
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • SSVC assessment updated
    Oct 13, 2026 · CVE Program (cve.org) e CISA ADP
  • Added to CISA KEV (detected)
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Record created in this database
    Oct 13, 2026 · CISA Known Exploited Vulnerabilities
  • Added to CISA KEV catalog
    Apr 12, 2026 · CISA
  • 2020
  • CVE published
    Aug 19, 2020 · adobe

Source activity

Repeated readings are counted rather than listed.

  • 3× References added · Oct 13, 2026 – Oct 13, 2026
  • 1× Official description updated · Oct 13, 2026 – Oct 13, 2026

References

8 on the record

Elsewhere on this site

Adobe
every CVE for this vendor
2026-04
what else CISA listed that month
Memory corruption
same class
CWE-416
other pages naming this weakness

Related CVEs (same products)

  • CVE-2020-9695 Acrobat Reader | Out-of-bounds Write (CWE-787) Jun 23, 2026
  • CVE-2020-9711 Acrobat Reader | Out-of-bounds Read (CWE-125) Jun 23, 2026
  • CVE-2020-9713 Acrobat Reader | Out-of-bounds Read (CWE-125) Jun 23, 2026
  • CVE-2026-47965 Acrobat Reader | Out-of-bounds Write (CWE-787) Jun 12, 2026
  • CVE-2026-47955 Acrobat Reader | Use After Free (CWE-416) Jun 9, 2026
  • CVE-2026-47961 Acrobat Reader | Out-of-bounds Read (CWE-125) Jun 9, 2026

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 record

Text assembled only from the fields above — no additional claims.

What should defenders know first?

CVE-2020-9715 is "Adobe Acrobat Use-After-Free Vulnerability", rated High. It affects Acrobat DC (Adobe); versions are in the scope table. It is in CISA KEV: there is evidence of real-world exploitation. CVSS 7.8 describes technical severity. EPSS 48.60% estimates the probability of exploitation in 30 days; neither replaces your asset context. First verify whether exposed or business-critical assets run the affected versions, apply vendor fixes or mitigations, and preserve logs for review.

Comments

Moderated technical discussion. Read the community guidelines.

No comments yet.

Sign in or create an account to comment and suggest corrections.