CVE-2016-1041
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 Reader and Acrobat before 11.0.16, Acrobat and Acrobat Reader DC Classic before 15.006.30172, and Acrobat and Acrobat Reader DC Continuous before 15.016.20039 on Windows and OS X allow attackers to bypass JavaScript API execution restrictions via unspecified vectors, a different vulnerability than CVE-2016-1038, CVE-2016-1039, CVE-2016-1040, CVE-2016-1042, CVE-2016-1044, CVE-2016-1062, and CVE-2016-1117.
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 a JavaScript API restriction bypass vulnerability in Adobe Reader and Acrobat. The vulnerability allows attackers to circumvent the built-in JavaScript API execution restrictions that are meant to limit what actions embedded JavaScript can perform within PDF documents, potentially enabling malicious script 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<= 11.0.15<= 15.006.30121<= 15.010.20060<= 15.006.30121<= 15.010.20060<= 11.0.15CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:C/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 Adobe product and versionOpen Adobe Reader or Acrobat, go to Help > About Adobe Reader/Acrobat to display the exact version number. Alternatively, check Programs and Features in Windows Control Panel or the Applications folder on Mac.Affected if The displayed version is 11.0.15 or earlier for Reader/Acrobat Classic, or 15.006.30121/15.010.20060 or earlier for DC versions.
-
Confirm product typeDetermine whether the installation is Adobe Reader, Adobe Acrobat Standard, or Adobe Acrobat Pro. This matters because the affected version ranges differ slightly between Reader and Acrobat.Affected if The product is Adobe Reader <= 11.0.15, Adobe Acrobat <= 11.0.15, Adobe Acrobat DC <= 15.006.30121, Adobe Acrobat DC <= 15.010.20060, or Adobe Acrobat Reader DC <= 15.006.30121/15.010.20060.
-
Verify JavaScript execution is enabledIn Adobe Reader or Acrobat, go to Edit > Preferences > JavaScript and confirm the 'Enable Adobe JavaScript' option is checked. This is the setting that allows embedded PDF JavaScript to execute.Affected if JavaScript is enabled in the application preferences, as this is the required condition for the vulnerability to be exploitable.
-
Check for recent PDF files with JavaScriptInspect recently opened PDF files using a hex editor or PDF analysis tool to search for '/JS' or '/JavaScript' dictionary entries within the PDF structure. This indicates the PDF contains embedded JavaScript.Affected if PDF files with embedded JavaScript have been opened, as the vulnerability allows malicious scripts in such PDFs to bypass API restrictions.
You are affected if your installed Adobe Reader or Acrobat version falls within the affected ranges (11.0.15 or earlier for Classic, 15.006.30121/15.010.20060 or earlier for DC) AND JavaScript is enabled in the application settings.
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 · scopedUpdate Adobe Reader and Acrobat to version 11.0.16 or later (Classic) / 15.006.30172 or later (DC Classic) / 15.016.20039 or later (DC Continuous).
Acrobat/Reader 11.0.16; Acrobat DC Classic 15.006.30172; Acrobat DC Continuous 15.016.20039
- Identify the exact product and version of Adobe Acrobat or Reader installed (11.x, DC Classic, or DC Continuous)
- Download the appropriate fixed version from the official Adobe security bulletin (apsb16-14) or the Adobe website
- For Acrobat/Reader 11.x: Upgrade to version 11.0.16 or later
- For Acrobat/Acrobat Reader DC Classic: Upgrade to version 15.006.30172 or later
- For Acrobat/Acrobat Reader DC Continuous: Upgrade to version 15.016.20039 or later
- Restart the application after installation
- Verify the installed version matches or exceeds the fixed version numbers
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.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 $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-1041 — 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-2016-1041 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