Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 15 Jun 2022.
AcrobatApplication · Adobe

CVE-2014-0546

CRITICAL · 9.8 CVSS v3.1 Published 2014-08-12
Fix available
A fix is available. Upgrade to 10.1.11 / 11.0.08 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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
Adobe Reader and Acrobat 10.x before 10.1.11 and 11.x before 11.0.08 on Windows allow attackers to bypass a sandbox protection mechanism, and consequently execute native code in a privileged context, via unspecified vectors.

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

This is a sandbox bypass vulnerability in Adobe Reader and Acrobat versions 10.x before 10.1.11 and 11.x before 11.0.08 on Windows. Attackers can circumvent the sandbox protection mechanism and execute native code in a privileged context, leading to complete system compromise.

MitigationApply the vendor-supplied security updates (Adobe Reader/Acrobat 10.1.11 or later for v10.x, and 11.0.08 or later for v11.x) or upgrade to the latest patched versions.

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.11>= 11.0, < 11.0.08
Acrobat ReaderApplication
Affected:>= 10.0, < 10.1.11>= 11.0, < 11.0.08

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
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 checks

Work through these to decide whether this CVE applies to you.

  1. Check if Adobe Acrobat or Reader is installed
    Open Command Prompt and run: wmic product where "name like 'Adobe%'" get name,version
    Affected if No Adobe products are listed, the system is not affected by this CVE
  2. Identify the exact Adobe product version
    Open Adobe Reader or Acrobat, go to Help > About Adobe Reader/Acrobat, or check the version in Programs and Features
    Affected if Version displays as 10.x (where x is any build below 10.1.11) or 11.x (where x is any build below 11.0.08)
  3. Query installed version via command line
    Run: wmic product where "name like 'Adobe Acrobat%' or name like 'Adobe Reader%'" get name,version
    Affected if Version returned is less than 10.1.11 (for 10.x versions) or less than 11.0.08 (for 11.x versions)
  4. Verify the sandbox feature status
    The vulnerability affects the sandbox protection. No user-configurable check exists; version is the definitive indicator of exposure
    Affected if Running a vulnerable version confirms the sandbox can potentially be bypassed

If Adobe Acrobat or Reader version is 10.0 through 10.1.10, or 11.0 through 11.0.07 on Windows, the sandbox bypass vulnerability is present and the system is affected.

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 10.1.11 / 11.0.08 or later
Fixed in 10.1.1111.0.08
Vendor patch helpx.adobe.com →
Interim mitigation

Apply the vendor-supplied security updates (Adobe Reader/Acrobat 10.1.11 or later for v10.x, and 11.0.08 or later for v11.x) or upgrade to the latest patched versions.

Recommended fix High confidence

Acrobat/Reader 10.1.11 (for 10.x branch); Acrobat/Reader 11.0.08 (for 11.x branch)

  1. Identify currently installed Adobe Acrobat or Reader version from Help > About menu
  2. For Adobe Acrobat/Reader 10.x users: Download and install version 10.1.11 from the official Adobe website
  3. For Adobe Acrobat/Reader 11.x users: Download and install version 11.0.08 from the official Adobe website
  4. Verify the update was successful by checking Help > About to confirm the version number
Caveat Security patch updates are typically backwards compatible; however, this is legacy software from 2014 and may have compatibility limitations with modern Windows versions

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

Fix this in Acrobat Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get it fixed fast

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2014-0546 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2014-0546 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