Outdated Adobe Acrobat or Reader

Hosts run Adobe Acrobat or Acrobat Reader builds that are missing security updates, so a crafted PDF opened by a user could run code.

SeverityHigh
CVSS 3.17.8 CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H Open in the calculator
CVSS 4.08.5 CVSS:4.0/AV:L/AC:L/AT:N/PR:N/UI:P/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N Open in the calculator
CWECWE-1395: Dependency on Vulnerable Third-Party Component
OWASP Top 10A03:2025 Software Supply Chain Failures
MITRE ATT&CKT1203 Exploitation for Client Execution, T1566.001 Spearphishing Attachment
CategoryOutdated Components

Description

One or more hosts run builds of Adobe Acrobat or Adobe Acrobat Reader that are missing security updates, or a product track that Adobe no longer supports. Acrobat and Reader are distributed in a Continuous track, which updates frequently and, by default, silently, and a Classic track, which receives quarterly updates; Classic releases reach end of support on fixed dates.

Adobe publishes security bulletins for Acrobat and Reader regularly, and most of their fixes address memory corruption, such as use-after-free and out-of-bounds write flaws, that can be triggered by opening a crafted PDF file. An attacker can send such a PDF by email or host it on a website and, if a user on an affected host opens it, run code with that user's privileges, gaining a foothold on the network. PDF files are routinely accepted and opened in business, which makes this an effective phishing vector, and Acrobat and Reader vulnerabilities such as CVE-2023-26369 have been exploited in the wild and are listed in CISA's Known Exploited Vulnerabilities (KEV) catalogue. Reader's Protected Mode sandbox makes exploitation harder, and removing administrative rights from users limits what a successful exploit gains.

The finding is identified by authenticated scans that read the installed product version, and scanners report one result per missing security bulletin. Updates commonly fail to arrive where automatic updating has been disabled in an enterprise deployment and nothing replaces it, where a Classic track installation has been left in place after its end of support, or where users have installed Reader themselves outside central management.

Remediation

Keep Acrobat and Reader current and supported:

  • Update every installation to the latest build of a supported track, using Adobe's updater or the organisation's patch management tool, and install future updates within the timescales of the patch management process.
  • Leave automatic updates enabled for Continuous track installations, or distribute Adobe's updates promptly where the enterprise configuration disables them.
  • Replace installations on Classic tracks that have reached end of support with a supported release.
  • Remove installations that users added outside central management, or bring them under it.
  • Keep Protected Mode and Protected View enabled, and disable Acrobat JavaScript where it is not needed, using the enterprise configuration settings that Adobe documents.

Confirm the fix by checking the version under Help, About in the product or in the management tool's inventory, and repeating the scan.

References


Add This Finding to Your Library

In Pental this write-up is in Settings, Library. Add to my library copies it into your own, rated in your firm's CVSS version, ready to put in your own words.

Free trial  ·  No card required

Only need the reporting? Our reporting tool is free and open source, with the same library.


More Patching and Outdated Software Findings

Every Patching and Outdated Software finding