CVE-2014-0546: Adobe Reader and Acrobat Sandbox Bypass
Adobe Reader and Acrobat · listed in the CISA catalog of actively exploited vulnerabilities since 2022-05-25.
- CVSS v3.1 (CISA ADP)
- 8.8
- high
- EPSS (exploit probability, 30 days)
- 22%
- higher than 97.7% of all CVEs
- Added to CISA KEV
- 2022-05-25
- US federal due date 2022-06-15
- Automatable (CISA SSVC)
- no
- technical impact: total
CVE-2014-0546 explained
CVE-2014-0546 is a sandbox bypass vulnerability in Adobe Reader and Acrobat on Windows. Attackers can escape the sandbox protection mechanism and execute native code in a privileged context. CISA lists it as known to be exploited, so unpatched installations face real risk.
Impact
A successful attacker can bypass the sandbox and run native code with elevated privileges. CISA rates the technical impact as total, meaning full control of the affected component. The attack works over the network with low complexity and no privileges, but requires user interaction. CISA does not consider it automatable, so exploitation at scale needs per-target steps. Attackers are known to exploit it; ransomware use is unknown.
Who is affected
The description names Adobe Reader and Acrobat 10.x before 10.1.11 and 11.x before 11.0.08 on Windows. The structured CVE record lists no affected versions for Adobe Reader and Acrobat and names no fixed version. Use the Adobe advisory to confirm which builds contain the fix.
Written with AI from the data on this page and checked against it automatically.
Official description
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.
CISA required action: Apply updates per vendor instructions.
CISA notes
How to fix it
- The CVE record names no fixed version – check the vendor advisory and CISA's required action for updates and mitigations.
- Vendor advisory: helpx.adobe.com/security/products/reader/apsb14-19.html
- CISA's deadline for US federal agencies: 2022-06-15 (passed) – a useful benchmark for everyone else, too.
What to do
- Apply Adobe's updates for Reader and Acrobat per vendor instructions, as CISA requires.
- Check the Adobe advisory to confirm the fixed build for each installed branch.
- Inventory all Windows systems running Adobe Reader or Acrobat, including older
10.xand11.xinstallations. - Replace installations that cannot be updated with a supported, patched version.
- Review systems that ran vulnerable versions for signs of compromise.
The CVE record names no fixed version, but this does not mean no fix exists. Follow CISA's required action to apply updates per vendor instructions, and use the Adobe advisory to identify the correct updated build. Until updates are confirmed on every system, limit use of the affected software and monitor endpoints for suspicious activity.
Written with AI from the data on this page and checked against it automatically.
CISA's assessment (SSVC)
- Exploitation
- Exploited in the wild
- Automatable
- No – each attack needs manual steps
- Technical impact
- Total – full control of the component or total information disclosure
Questions about CVE-2014-0546
- Is CVE-2014-0546 being exploited?
- Yes. CISA added it to its Known Exploited Vulnerabilities catalog on 2022-05-25. Whether it has been used in ransomware campaigns is unknown.
- Which platforms are affected?
- The description states Adobe Reader and Acrobat on Windows are affected, specifically
10.xbefore10.1.11and11.xbefore11.0.08. - What was the deadline for US federal agencies?
- CISA set a due date of 2022-06-15 for federal agencies to apply updates per vendor instructions.
Written with AI from the data on this page and checked against it automatically.
References
Trackers and catalogs
Data: CISA Known Exploited Vulnerabilities (public domain) · CVE Program records incl. CISA ADP enrichment · OSV.dev (CC BY 4.0) incl. Ubuntu and Debian security data · FIRST EPSS · endoflife.date. Updated automatically – facts last changed 2026-11-22. Always confirm with the vendor's or distribution's advisory before patching.