dbcve.org
Acrobat DcApplication · Adobe

CVE-2018-12776

HIGH · 8.8 CVSS v3.0 Published 2018-07-20
Fix available
A fix is available. Upgrade to after 18.011.20040 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier versions have a Use-after-free vulnerability. Successful exploitation could lead to arbitrary code execution in the context of the current user.

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 use-after-free vulnerability exists in Adobe Acrobat and Reader versions 2018.011.20040 and earlier, 2017.011.30080 and earlier, and 2015.006.30418 and earlier. The vulnerability allows attackers to manipulate memory after it has been freed, potentially leading to arbitrary code execution in the context of the current user.

MitigationApply the vendor-supplied security patches for Adobe Acrobat and Reader to upgrade to a fixed version, or upgrade to the latest release of the software.

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.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080
Acrobat Reader DcApplication
Affected:>= 15.006.30060, <= 15.006.30418>= 15.008.20082, <= 18.011.20040>= 17.011.30059, <= 17.011.30080

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/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. Identify installed Adobe Acrobat or Reader product
    Open the application, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The version number appears in the title bar of the About dialog.
    Affected if The product is Adobe Acrobat Dc or Adobe Acrobat Reader Dc.
  2. Determine the exact version number
    Note the version string shown (for example: 18.011.20040, 17.011.30080, 15.006.30418). On Windows, you can also right-click the executable (Acrobat.exe or AcroRd32.exe), select Properties, and check the Details tab for the Product Version.
    Affected if The version matches the affected ranges: 15.006.30060 to 15.006.30418, 15.008.20082 to 18.011.20040, or 17.011.30059 to 17.011.30080.
  3. Verify the product edition and update channel
    Confirm whether you are running the Continuous track or the Classic track. In the application, go to Help > Check for Updates or view the update preferences. The Continuous track uses versions like 18.x, while Classic uses 15.x and 17.x.
    Affected if The product is the Continuous track (18.x or higher within the range) or Classic track (15.x, 17.x versions within the range).
  4. Confirm the application is actively used or configured
    Check if Adobe Acrobat or Reader is installed as a default PDF handler or frequently used. Look for the application in Start Menu, or check Add/Remove Programs (Windows) or Applications folder (macOS).
    Affected if The application is installed and available for use on the system.

You are affected if Adobe Acrobat Dc or Adobe Acrobat Reader Dc is installed with any version between 15.006.30060 and 15.006.30418, between 15.008.20082 and 18.011.20040, or between 17.011.30059 and 17.011.30080.

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 18.011.20040
Interim mitigation

Apply the vendor-supplied security patches for Adobe Acrobat and Reader to upgrade to a fixed version, or upgrade to the latest release of the software.

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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