dbcve.org
Acrobat DcApplication · Adobe

CVE-2019-7131

CRITICAL · 9.8 CVSS v3.1 Published 2020-01-28
Fix available
A fix is available. Upgrade to 15.006.30464 / 17.011.30113 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

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 2019.010.20064 and earlier, 2019.010.20064 and earlier, 2017.011.30110 and earlier version, and 2015.006.30461 and earlier have a type confusion vulnerability. Successful exploitation could lead to arbitrary code execution.

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

A type confusion vulnerability in Adobe Acrobat and Reader allows attackers to manipulate object type handling, bypassing security boundaries and achieving arbitrary code execution with no user interaction beyond opening a malicious PDF.

MitigationUpdate Adobe Acrobat and Reader to versions later than 2019.010.20064, 2017.011.30110, and 2015.006.30461 to patch the type confusion flaw.

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:>= 15.006.30060, < 15.006.30464>= 15.008.20082, < 19.010.20069>= 17.011.30059, < 17.011.30113
Acrobat Reader DcApplication
Affected:>= 15.006.30060, < 15.006.30464>= 15.008.20082, < 19.010.20069>= 17.011.30059, < 17.011.30113

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
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

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

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. Locate Adobe Acrobat or Reader installation
    Open Adobe Acrobat/Reader, go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat) to view the exact version number. Alternatively, check Programs and Features in Windows Control Panel or the Applications folder on macOS.
    Affected if The installed product is Adobe Acrobat DC or Adobe Acrobat Reader DC but the version displayed is not shown
  2. Identify the product track and version
    Note the four-digit version number shown (for example, 15.006.30060 or 17.011.30059). The first two digits indicate the track: 15.x = Classic 2015, 17.x = 2017, 19.x = Continuous/2019.
    Affected if The product is Adobe Acrobat DC or Reader DC with a version starting with 15.x, 17.x, or 19.x
  3. Compare against vulnerable version ranges
    Check if the installed version falls within any of these ranges: 15.006.30060 through 15.006.30463; 15.008.20082 through 19.010.20068; 17.011.30059 through 17.011.30112.
    Affected if The installed version is greater than or equal to 15.006.30060 and less than 15.006.30464, OR greater than or equal to 15.008.20082 and less than 19.010.20069, OR greater than or equal to 17.011.30059 and less than 17.011.30113
  4. Verify if the software handles PDF files
    Confirm the software is used to open or process PDF documents. The vulnerability is triggered when the application parses a maliciously crafted PDF file.
    Affected if Adobe Acrobat or Reader is installed and configured to open PDF files, with no additional security software blocking unknown PDFs

A user is affected if they have Adobe Acrobat DC or Reader DC installed with a version matching any of the three vulnerable ranges, and they open untrusted PDF files.

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.

dbcve · scoped
Upgrade available Upgrade to 15.006.30464 / 17.011.30113 / 19.010.20069 or later
Fixed in 15.006.3046417.011.3011319.010.20069
Interim mitigation

Update Adobe Acrobat and Reader to versions later than 2019.010.20064, 2017.011.30110, and 2015.006.30461 to patch the type confusion flaw.

Recommended fix High confidence

Adobe Acrobat/Reader DC 2019: 19.010.20069 or later (recommended: 19.012.20036+); 2017: 17.011.30113 or later; 2015: 15.006.30464 or later

  1. 1. Identify the currently installed Adobe Acrobat or Adobe Acrobat Reader DC version by opening the application and navigating to Help > About Adobe Acrobat/Reader DC
  2. 2. Determine which version branch (2015, 2017, or 2019) the installation belongs to based on the version number
  3. 3. For Adobe Acrobat DC or Acrobat Reader DC version 2015.x: Upgrade to version 15.006.30464 or later (preferably the latest 2015 release: 15.006.30497 or later)
  4. 4. For Adobe Acrobat DC or Acrobat Reader DC version 2017.x: Upgrade to version 17.011.30113 or later (preferably the latest 2017 release: 17.011.30145 or later)
  5. 5. For Adobe Acrobat DC or Acrobat Reader DC version 2019.x: Upgrade to version 19.010.20069 or later (preferably the latest 2019 release: 19.012.20036 or later)
  6. 6. Download the appropriate fixed version from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
  7. 7. Close all Adobe applications before running the installer
  8. 8. After upgrading, verify the version by checking Help > About to confirm the installation was successful
Caveat Standard Adobe update - minimal risk; may require acceptance of new license terms; ensure compatibility with existing PDF workflows and plugins before deploying enterprise-wide

Generated from the published advisory — verify against the referenced sources before acting.

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

Get it on GitHub Scan in the browser

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-2019-7131 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