CVE-2019-16460
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 · uneditedAdobe Acrobat and Reader versions , 2019.021.20056 and earlier, 2017.011.30152 and earlier, 2017.011.30155 and earlier version, 2017.011.30152 and earlier, and 2015.006.30505 and earlier have an untrusted pointer dereference 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 confidenceThis is an untrusted pointer dereference vulnerability in Adobe Acrobat and Reader that allows attackers to dereference invalid memory pointers. Successful exploitation enables arbitrary code execution in the context of the current user. The vulnerability affects multiple older versions across the 2015, 2017, and 2019 product lines.
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>= 15.006.30060, < 15.006.30508>= 15.008.20082, < 19.021.20058>= 17.011.30059, < 17.011.30156>= 15.006.30060, < 15.006.30508>= 15.008.20082, < 19.021.20058>= 17.011.30059, < 17.011.30156CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify installed Adobe productOpen Windows Control Panel and look for 'Adobe Acrobat DC' or 'Adobe Acrobat Reader DC' in Programs and Features, or check the application's Help > About menuAffected if Neither Adobe Acrobat DC nor Adobe Acrobat Reader DC is installed - not applicable
-
Determine exact product versionIn the application, go to Help > About Adobe Acrobat DC (or Reader DC). The version number displays as something like 15.x.x.x, 17.x.x.x, or 19.x.x.x. Alternatively, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\Version (or for Reader: ...\Adobe Acrobat Reader\DC\Version)Affected if No version number can be determined - verify the product is correctly installed
-
Compare version against affected rangesMatch your installed version number to the affected ranges: 15.006.30060 through 15.006.30507 (inclusive), 15.008.20082 through 19.021.20057 (inclusive), or 17.011.30059 through 17.011.30155 (inclusive). Versions below 15.006.30060 are not in the affected rangeAffected if The installed version falls within any of these ranges: 15.006.30060-15.006.30507, 15.008.20082-19.021.20057, or 17.011.30059-17.011.30155
If Adobe Acrobat DC or Reader DC is installed with a version matching any of the three vulnerable ranges, the system is affected by CVE-2019-16460 and should be updated.
Generated from the published advisory. Verify against your own configuration.
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 · scoped15.006.3050817.011.3015619.021.20058
Immediately update Adobe Acrobat and Reader to the latest patched versions beyond 2019.021.20056, 2017.011.30152, and 2015.006.30505. Prioritize patching for systems that process untrusted PDF documents or are exposed to external networks.
15.006.30508 or later (Classic 2015); 17.011.30156 or later (2017); 19.021.20058 or later (2019/Continuous)
- Identify the currently installed Adobe Acrobat or Acrobat Reader version via Help > About Adobe Acrobat/Reader
- For Acrobat DC/Reader DC Classic track (version 15.006.x): upgrade to version 15.006.30508 or later
- For Acrobat DC/Reader DC Continuous track (version 15.008.x - 19.x): upgrade to version 19.021.20058 or later
- For Acrobat DC/Reader DC 2017 track (version 17.011.x): upgrade to version 17.011.30156 or later
- Alternatively, download the latest version from https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
- Verify the update was successful by checking Help > About after restarting the application
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2019-16460 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2019-16460 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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