dbcve.org
Acrobat DcApplication · Adobe

CVE-2019-7128

CRITICAL · 9.8 CVSS v3.0 Published 2019-05-23
Fix available
A fix is available. Upgrade to after 19.010.20098 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click Patch available

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.20098 and earlier, 2019.010.20098 and earlier, 2017.011.30127 and earlier version, and 2015.006.30482 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
How this class of weakness works · CWE-843

A resource is accessed as one type when it was actually allocated as another, so the code misreads memory layout — in interpreters and language runtimes this is frequently a direct path to code execution. It often arises from unchecked casts on attacker-influenced objects. The fix is strict type checks before casts and memory-safe access patterns.

General guidance for the type confusion class — the official description and references above are authoritative for this specific CVE. Want a bespoke review and a reviewed fix? Ask our team →

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.30482>= 15.008.20082, <= 19.010.20098>= 17.011.30056, <= 17.011.30127
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30482>= 15.008.20082, <= 19.010.20098>= 17.011.30059, <= 17.011.30127

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.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

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 a release after 19.010.20098
Vendor patch helpx.adobe.com →
Recommended fix High confidence

Upgrade to Adobe Acrobat/Reader 2019.010.20099 or later, 2017.011.30128 or later, or 2015.006.30483 or later (depending on your version track)

  1. 1. Verify current Adobe Acrobat or Adobe Reader version by navigating to Help > About Adobe Acrobat/Reader
  2. 2. Identify which version track you are on (2015, 2017, or 2019) based on the affected version ranges provided
  3. 3. Download the patched version from the official Adobe security bulletin APSB19-17 at https://helpx.adobe.com/security/products/acrobat/apsb19-17.html
  4. 4. Close all Adobe applications before installing the update
  5. 5. Run the installer and follow the prompts to complete the installation
  6. 6. Restart the system after installation completes
  7. 7. Verify the version has been updated to a fixed release (2015.006.30483+, 2017.011.30128+, or 2019.010.20099+)
Caveat Standard Adobe update - minimal risk; ensure backups of critical PDFs exist before major version upgrades

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

We can identify the exact fixed release, upgrade, and verify it in staging — typical engagement from $2,300. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2019-7128 — 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-7128 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