⚠ Reference material — not professional advice. Test in staging, back up first, verify against your specific version. Use your own judgment for your environment.
● High · CVSS 8.8 ⚠ ACTIVELY EXPLOITED — CISA KEV

How to Fix CVE-2014-0546: Security Vulnerability in Reader And Acrobat

Other vulnerabilities in the same area that are worth patching alongside this one:

*By Sai Kiran Pandrala*

⚡ At a glance
SeverityCVSS 8.8 - High
Actively exploited?Yes, listed in CISA KEV (added 2022-05-25)
Affectedn/a: n/a
Fixed inSee vendor advisory for the patched build
Type (CWE)Not classified by CWE
Patch immediately. CISA's Known Exploited Vulnerabilities catalog lists this CVE, which means active exploitation has been confirmed. CISA KEV entry added 2022-05-25, federal due date 2022-06-15.

What is CVE-2014-0546?

CVE-2014-0546 is a security vulnerability in Reader And Acrobat from Adobe. 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.

Why this CVE matters

This CVE sits on CISA's Known Exploited Vulnerabilities catalog, which only happens after active exploitation is observed in the wild. The security vulnerability class of flaw gives attackers a reliable foothold against vulnerable instances of Reader And Acrobat. If your deployment matches the affected versions, treat any window of unpatched exposure as compromise-likely and review logs accordingly.

Am I affected?

Run the version check that matches your platform. If the installed build sits inside the affected range from the table above, the fix applies to you.


# Linux package check
dpkg -s readerandacrobat 2>/dev/null | grep -i version    # Debian / Ubuntu
rpm -q readerandacrobat 2>/dev/null                       # RHEL / Rocky


# Windows version check
Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'Reader And Acrobat' } | Select-Object Name,Version

How to fix CVE-2014-0546

Apply the patched build the vendor names in the advisory. The commands below are starting points keyed to common platforms - adapt the package name and target version to your environment.

Windows (PowerShell, run as administrator)


# Vendor advisory: http://helpx.adobe.com/security/products/reader/apsb14-19.html
# Make sure Windows Update is current. For monthly rollups this is the safest path.
Install-Module -Name PSWindowsUpdate -Force -SkipPublisherCheck -Confirm:$false
Import-Module PSWindowsUpdate
Get-WindowsUpdate -KBArticleID <KB-from-advisory>
Install-WindowsUpdate -KBArticleID <KB-from-advisory> -AcceptAll -AutoReboot

# Confirm the KB landed
Get-HotFix | Where-Object { $_.HotFixID -eq 'KB<id>' }

# Or, for an MSU file downloaded from the Microsoft Update Catalog:
wusa.exe C:\Patches\windows10.0-kb<id>-x64.msu /quiet /norestart
shutdown /r /t 60

PowerShell detect/upgrade/verify/log (Windows)


# CVE-2014-0546 remediation runner — adapt the version checks to your environment.
$log = "C:\Logs\CVE-2014-0546-fix.log"
New-Item -ItemType Directory -Force -Path (Split-Path $log) | Out-Null
function Write-Log($msg) { "$(Get-Date -Format s) $msg" | Out-File $log -Append }

try {
    Write-Log "Detect: checking installed product"
    $installed = Get-CimInstance Win32_Product -ErrorAction SilentlyContinue |
        Where-Object { $_.Name -match 'product' }
    if (-not $installed) { Write-Log "Product not installed; nothing to do"; return }
    Write-Log "Found version $($installed.Version)"

    Write-Log "Backup: copying program files and registry hive"
    $stamp = Get-Date -Format yyyyMMdd-HHmm
    $backup = "C:\Backup\CVE-2014-0546-$stamp"
    New-Item -ItemType Directory -Force -Path $backup | Out-Null
    Copy-Item $installed.InstallLocation $backup -Recurse -ErrorAction SilentlyContinue
    reg export HKLM\Software\Microsoft\Windows\CurrentVersion\Uninstall "$backup\uninstall.reg" /y | Out-Null

    Write-Log "Upgrade: install patched build via vendor MSI / Windows Update"
    # Example MSI:  Start-Process msiexec.exe -ArgumentList '/i C:\Patches\product-patched.msi /qn /norestart' -Wait
    Install-WindowsUpdate -AcceptAll -AutoReboot -ErrorAction SilentlyContinue

    Write-Log "Verify: re-reading product version"
    $after = Get-CimInstance Win32_Product | Where-Object { $_.Name -match 'product' }
    Write-Log "Post-patch version: $($after.Version)"
    if ($after.Version -ne $installed.Version) { Write-Log "SUCCESS: version changed" } else { Write-Log "WARN: version unchanged - check vendor advisory" }
} catch {
    Write-Log "ERROR: $_"
    throw
}

After the upgrade, restart any service that loads the patched binary so the new code is actually running.

If you can't patch immediately

Patching is the only durable fix. These mitigations cut exposure while the change window is scheduled, they do not remove the vulnerability.

Windows: disable the vulnerable feature via registry


# Vendor advisory: http://helpx.adobe.com/security/products/reader/apsb14-19.html
# Replace <Component> / <Setting> with the exact key from the vendor advisory.
# Always export the key first so you can roll back.
reg export "HKLM\SOFTWARE\Vendor\Product" "C:\Backup\preFix-CVE-2014-0546.reg" /y
Set-ItemProperty -Path "HKLM:\SOFTWARE\Vendor\Product" -Name "Disable<Setting>" -Value 1 -Type DWord
Restart-Service -Name "<service-name>" -Force

How to verify the fix worked

After applying the patched build, confirm the version string matches the fixed release named in the Adobe advisory.


dpkg -s readerandacrobat | grep -i version       # Debian / Ubuntu
rpm -q readerandacrobat                          # RHEL / Rocky


Get-HotFix | Sort-Object InstalledOn -Descending | Select-Object -First 5

Run an authenticated vulnerability scan with a current signature set and confirm the scanner no longer flags CVE-2014-0546. For internet-facing deployments that were unpatched during the disclosure window, review logs for the affected endpoints over the full exposure period and rotate any credentials the vulnerable process could touch.

Frequently asked questions

Is CVE-2014-0546 being exploited in the wild?

Yes. CISA added CVE-2014-0546 to the Known Exploited Vulnerabilities catalog, which means active exploitation has been confirmed.

Will a firewall rule or WAF signature fully mitigate CVE-2014-0546?

No. Network-layer filters slow opportunistic scanners and block a subset of payloads, but a focused attacker who knows the bug will work around them. The vendor patch is the only durable fix.

Do I need to assume compromise if the affected service was internet-facing and unpatched?

For a CVE that CISA confirms is under active exploitation, yes. Review logs for the affected endpoints over the entire exposure window, rotate credentials the vulnerable process could read, and look for unexpected accounts, scheduled tasks, or outbound connections.

References

*This guide was assembled from the official vendor advisory, the NVD record, and the CISA KEV catalog entry on 2026-05-25. Always confirm against the vendor advisory before applying changes in production.*