Acrobat DcApplication · Adobe

CVE-2020-9713

MEDIUM · 5.5 CVSS v3.1 Published 2026-06-23
Fix available
A fix is available. Upgrade to after 20.009.20074 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges 8 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Adobe Acrobat and Reader versions 2020.009.20074 and earlier, 2020.001.30002, 2017.011.30171 and earlier, and 2015.006.30523 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

This is an out-of-bounds read vulnerability in Adobe Acrobat and Reader. When a victim opens a specially crafted malicious PDF file, the application reads memory outside allocated buffer bounds, potentially exposing sensitive information from the application's memory space.

MitigationApply the official Adobe security update/patch for Acrobat and Reader. Additionally, enforce policies to prevent opening untrusted or unexpected PDF files from unknown sources.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Acrobat DcApplication
Affected:<= 20.009.20074>= 15.000.0000, <= 15.006.30523>= 17.009.20044, <= 17.011.30171= 20.001.30002
Acrobat ReaderApplication
Affected:= 20.001.30002
Acrobat Reader DcApplication
Affected:<= 20.009.20074>= 15.000.0000, <= 15.006.30523>= 17.009.20044, <= 17.011.30171

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
None
Availability
None

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check if Adobe Acrobat or Reader is installed
    On Windows, check for the presence of Adobe Acrobat or Adobe Reader in Programs and Features, or check common installation paths such as C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\
    Affected if Either Adobe Acrobat or Adobe Reader is installed on the system
  2. Determine the installed version of Adobe Acrobat DC
    Open Adobe Acrobat DC, go to Help > About Adobe Acrobat DC, or right-click the Acrobat icon and select Help > About to view the exact version number
    Affected if The version displayed is <= 20.009.20074, or = 20.001.30002, or falls within 15.000.0000 to 15.006.30523, or falls within 17.009.20044 to 17.011.30171
  3. Determine the installed version of Adobe Acrobat Reader DC
    Open Adobe Acrobat Reader DC, go to Help > About Adobe Acrobat Reader DC, or right-click the Reader icon and select Help > About to view the exact version number
    Affected if The version displayed is <= 20.009.20074, or falls within 15.000.0000 to 15.006.30523, or falls within 17.009.20044 to 17.011.30171
  4. Determine the installed version of Adobe Acrobat Reader (classic)
    Open Adobe Acrobat Reader, go to Help > About Adobe Acrobat Reader to view the exact version number
    Affected if The version displayed is exactly 20.001.30002

A user is affected if Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Acrobat Reader is installed with a version matching any of the listed affected ranges.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 20.009.20074
Interim mitigation

Apply the official Adobe security update/patch for Acrobat and Reader. Additionally, enforce policies to prevent opening untrusted or unexpected PDF files from unknown sources.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2020-9713 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2020-9713 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data