dbcve.org
AcrobatApplication · Adobe

CVE-2015-6691

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-5586, CVE-2015-6683, CVE-2015-6684, CVE-2015-6687, CVE-2015-6688, CVE-2015-6689, CVE-2015-6690, 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. The flaw exists in versions 10.x before 10.1.16, 11.x before 11.0.13, and DC versions before the specified thresholds on Windows and OS X.

MitigationUpdate Adobe Reader and Acrobat to version 10.1.16, 11.0.13, or DC versions 2015.006.30094 (Classic) / 2015.009.20069 (Continuous) or later to remediate this vulnerability.

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 Reader or Acrobat, then go to Help > About (or press Ctrl+8). Alternatively, on Windows check the registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\[version] or HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Reader\[version] for the version value.
    Affected if The product is Adobe Reader or Adobe Acrobat (any variant).
  2. Determine exact version number
    Note the full version string displayed in the About dialog or registry value. For DC versions, also identify whether it is the Classic or Continuous track by checking the installation folder structure or registry key: HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\DC\VersionMax.
    Affected if Version cannot be determined.
  3. Compare Classic/Acrobat 10.x version
    For Adobe Acrobat 10.x or Reader 10.x: compare your version against 10.1.16. Versions 10.0 through 10.1.15 are affected.
    Affected if Installed version is >= 10.0 and <= 10.1.15.
  4. Compare Classic/Acrobat 11.x version
    For Adobe Acrobat 11.x or Reader 11.x (non-DC): compare your version against 11.0.13. Versions 11.0.0 through 11.0.12 are affected.
    Affected if Installed version is >= 11.0.0 and <= 11.0.12.
  5. Compare DC (Classic track) version
    For Adobe Acrobat/Reader DC Classic track: check if version is >= 15.006.30060 and < 15.006.30094. Versions 15.006.30060 through 15.006.30093 are affected.
    Affected if Installed DC Classic version is >= 15.006.30060 and < 15.006.30094.
  6. Compare DC (Continuous) version
    For Adobe Acrobat/Reader DC Continuous track: check if version is >= 15.008.20082 and < 15.009.20069. Versions 15.008.20082 through 15.009.20068 are affected.
    Affected if Installed DC Continuous version is >= 15.008.20082 and < 15.009.20069.

You are affected if you have Adobe Reader or Adobe Acrobat installed with version 10.0-10.1.15, 11.0.0-11.0.12, DC Classic 15.006.30060-15.006.30093, or DC Continuous 15.008.20082-15.009.20068.

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

Update Adobe Reader and Acrobat to version 10.1.16, 11.0.13, or DC versions 2015.006.30094 (Classic) / 2015.009.20069 (Continuous) or later to remediate this vulnerability.

Recommended fix High confidence

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

  1. 1. Identify the exact Adobe Acrobat or Adobe Reader version currently installed (Help > About Adobe Acrobat/Reader)
  2. 2. Determine the product track: Classic (Continuous) or DC Classic based on version number
  3. 3. For Acrobat/Reader 10.x: Upgrade to version 10.1.16 or later
  4. 4. For Acrobat/Reader 11.x: Upgrade to version 11.0.13 or later
  5. 5. For Acrobat/Reader DC Classic (versions 15.006.30060-15.006.30093): Upgrade to version 2015.006.30094 or later
  6. 6. For Acrobat/Reader DC Continuous (versions 15.008.20082-15.009.20068): Upgrade to version 2015.009.20069 or later
  7. 7. Download the appropriate fixed version from the official Adobe security bulletin APSB15-24 at https://helpx.adobe.com/security/products/acrobat/apsb15-24.html
  8. 8. Close all Adobe applications before installing the update
Caveat No known breaking changes - this is a security patch upgrade with bug fixes

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation4.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
32.0 hours of engineering $5,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 $8,960.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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