dbcve.org
AcrobatApplication · Adobe

CVE-2015-5586

HIGH · 10.0 CVSS v2.0 Published 2015-10-14
Fix available
A fix is available. Upgrade to 15.006.30094 / 15.009.20069 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
Use-after-free vulnerability in Adobe Reader and Acrobat 10.x before 10.1.16 and 11.x before 11.0.13, Acrobat and Acrobat Reader DC Classic before 2015.006.30094, and Acrobat and Acrobat Reader DC Continuous before 2015.009.20069 on Windows and OS X allows attackers to execute arbitrary code via unspecified vectors, a different vulnerability than CVE-2015-6683, CVE-2015-6684, CVE-2015-6687, CVE-2015-6688, CVE-2015-6689, CVE-2015-6690, CVE-2015-6691, CVE-2015-7615, CVE-2015-7617, and CVE-2015-7621.

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 · moderate confidence

A use-after-free vulnerability in Adobe Reader and Acrobat allows attackers to execute arbitrary code via unspecified vectors, affecting versions 10.x before 10.1.16, 11.x before 11.0.13, and DC versions (Classic before 2015.006.30094, Continuous before 2015.009.20069) on Windows and OS X.

MitigationUpgrade to Adobe Reader/Acrobat 10.1.16, 11.0.13, or DC Classic 2015.006.30094/DC Continuous 2015.009.20069 or later to remediate this use-after-free vulnerability enabling arbitrary code execution.

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
AcrobatApplication
Affected:>= 10.0, <= 10.1.15>= 11.0.0, <= 11.0.12
Acrobat DcApplication
Affected:>= 15.006.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069
Acrobat ReaderApplication
Affected:>= 10.0, <= 10.1.15>= 11.0.0, <= 11.0.12
Acrobat Reader DcApplication
Affected:>= 15.006.30060, < 15.006.30094>= 15.008.20082, < 15.009.20069

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
Authentication
None
Confidentiality
Complete
Integrity
Complete
Availability
Complete

AV:N/AC:L/Au:N/C:C/I:C/A:C

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 product
    Open Adobe Acrobat or Adobe Reader and go to Help > About Adobe Acrobat (or Reader) to view the version number. Alternatively, on Windows right-click the executable in Program Files and select Properties > Details to see the File Version.
    Affected if The product is Adobe Acrobat or Adobe Reader (standard or DC variant)
  2. Confirm exact version number
    Note the full version number displayed (for example: 10.1.15, 11.0.12, 15.006.30060, or 15.008.20082). Record whether it is a Classic or Continuous release by examining the version pattern.
    Affected if The product is any release of Adobe Acrobat or Adobe Reader
  3. Compare against affected version ranges
    Match your installed version to these ranges: Acrobat/Reader 10.x versions 10.0 through 10.1.15; 11.x versions 11.0.0 through 11.0.12; DC Classic versions 15.006.30060 through 15.006.30093; DC Continuous versions 15.008.20082 through 15.009.20068.
    Affected if Your installed version falls within any of these ranges
  4. Verify product variant (standard vs DC)
    DC versions contain 'DC' in their name or version string. Classic releases have year-based numbering (like 2015.006.x). Standard releases are 10.x or 11.x without DC designation.
    Affected if The product is DC variant and version falls in 15.006.30060-15.006.30093 or 15.008.20082-15.009.20068 range

You are affected if Adobe Acrobat or Adobe Reader (standard or DC) is installed with a version between 10.0 and 10.1.15, between 11.0.0 and 11.0.12, between 15.006.30060 and 15.006.30093, or between 15.008.20082 and 15.009.20068 on Windows or OS X.

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.30094 / 15.009.20069 or later
Fixed in 15.006.3009415.009.20069
Vendor patch helpx.adobe.com →
Interim mitigation

Upgrade to Adobe Reader/Acrobat 10.1.16, 11.0.13, or DC Classic 2015.006.30094/DC Continuous 2015.009.20069 or later to remediate this use-after-free vulnerability enabling arbitrary code execution.

Recommended fix High confidence

Adobe Acrobat/Reader 10.1.16+, 11.0.13+, DC Classic 2015.006.30094+, or DC Continuous 2015.009.20069+

  1. Identify the exact installed Adobe Acrobat or Reader version from Help > About menu
  2. For Adobe Acrobat/Reader 10.x: Upgrade to version 10.1.16 or later
  3. For Adobe Acrobat/Reader 11.x: Upgrade to version 11.0.13 or later
  4. For Adobe Acrobat/Reader DC Classic: Upgrade to version 2015.006.30094 or later
  5. For Adobe Acrobat/Reader DC Continuous: Upgrade to version 2015.009.20069 or later
  6. Download the appropriate updated version from the official Adobe website at https://get.adobe.com/reader/ or https://get.adobe.com/acrobat/
  7. Install the update and restart the application
  8. Verify the version has been updated to a fixed release
Caveat Adobe periodically retires older product versions; ensure your operating system meets the requirements for the new version before upgrading

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,380
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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