dbcve.org
Acrobat DcApplication · Adobe

CVE-2026-47952

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 24.001.30383 / 26.001.21662 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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
Acrobat Reader versions 24.001.30365, 26.001.21651 and earlier are affected by a Heap-based Buffer Overflow vulnerability that could result in arbitrary code execution in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.

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 confidence

Heap-based buffer overflow vulnerability in Adobe Acrobat Reader when parsing maliciously crafted PDF files. Successful exploitation allows arbitrary code execution in the context of the current user. Requires victim to open a specially crafted file.

MitigationUpdate Adobe Acrobat Reader to version 24.001.30366 or later for the 24.x branch, or 26.001.201652 or later for the 26.x branch. Avoid opening untrusted PDF files until patched.

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
Acrobat DcApplication
Affected:>= 15.008.20082, < 26.001.21662
Acrobat Reader DcApplication
Affected:>= 15.008.20082, < 26.001.21662
AcrobatApplication
Affected:>= 24.0.0, < 24.001.30383

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
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/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
    On Windows, open Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Microsoft\Windows\CurrentVersion\Uninstall. Look for keys with DisplayName containing 'Adobe Acrobat' or 'Adobe Reader'. On macOS, check /Applications for Adobe Acrobat or Adobe Reader.app.
    Affected if No Adobe Acrobat or Reader installation is found, the system is not affected by this CVE.
  2. Determine the installed version
    In Windows Registry, locate the Adobe installation key found in the previous step and read the DisplayVersion value. Alternatively, right-click the Adobe executable in Program Files, select Properties, and view the Details tab for the Product Version.
    Affected if Unable to determine the installed version, proceed to manual verification required.
  3. Compare against affected version ranges
    Match the installed version to the following vulnerable ranges: Adobe Acrobat DC / Acrobat Reader DC: 15.008.20082 through 26.001.21661; Adobe Acrobat (standalone): 24.0.0 through 24.001.30382. Versions below 15.008.20082 or at/above 26.001.21662 (for DC) or 24.001.30383 (for version 24) are NOT affected.
    Affected if Installed version falls within 15.008.20082 to 26.001.21661 (for DC products) or 24.0.0 to 24.001.30382 (for Acrobat), the system is vulnerable.
  4. Verify PDF handling is the attack vector
    This vulnerability is triggered specifically when a user opens a specially crafted malicious PDF file. There is no configuration or service setting to check; the flaw exists in the PDF parsing logic of the application itself.
    Affected if The vulnerability can only be triggered if a user opens a malicious PDF file with a vulnerable version of Adobe Acrobat or Reader installed.

A system is affected if Adobe Acrobat DC, Acrobat Reader DC, or Adobe Acrobat is installed with a version between 15.008.20082 and 26.001.21661 (for DC products) or between 24.0.0 and 24.001.30382 (for version 24), and a user opens a specially crafted malicious PDF file.

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 24.001.30383 / 26.001.21662 or later
Fixed in 24.001.3038326.001.21662
Interim mitigation

Update Adobe Acrobat Reader to version 24.001.30366 or later for the 24.x branch, or 26.001.201652 or later for the 26.x branch. Avoid opening untrusted PDF files until patched.

Recommended fix High confidence

Acrobat DC/Acrobat Reader DC: upgrade to 26.001.21662 or later; Acrobat (24.x): upgrade to 24.001.30383 or later

  1. 1. Determine the currently installed Adobe Acrobat or Acrobat Reader version by opening the application and navigating to Help > About Adobe Acrobat (or Reader)
  2. 2. Identify which product line applies to your installation (Acrobat DC, Acrobat Reader DC, or Acrobat)
  3. 3. For Acrobat DC or Acrobat Reader DC users: Navigate to helpx.adobe.com and download version 26.001.21662 or later
  4. 4. For Acrobat (24.x) users: Navigate to helpx.adobe.com and download version 24.001.30383 or later
  5. 5. Close all Adobe applications before running the installer
  6. 6. Run the installer with administrative privileges
  7. 7. Restart the Adobe application after installation completes
  8. 8. Verify the installed version matches or exceeds the required fixed version by checking Help > About

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing3.0 h
  • Review / QA2.0 h
14.0 hours of engineering $2,490
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47952 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-2026-47952 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