dbcve.org
Acrobat DcApplication · Adobe

CVE-2026-47921

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 Use After Free 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

Adobe Acrobat Reader contains a Use After Free vulnerability where the software continues to use a memory pointer after it has been freed, allowing an attacker to manipulate heap memory and achieve arbitrary code execution. The attacker must craft a malicious PDF file that triggers the UAF condition when opened by the victim.

MitigationUpdate Adobe Acrobat Reader to a version later than 26.001.21651 (or 24.001.30366+) to patch the vulnerability. Users should avoid opening untrusted PDF files until the update is applied.

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, check for the application in Program Files (e.g., C:\Program Files\Adobe\Acrobat DC or C:\Program Files (x86)\Adobe\Acrobat Reader DC). On macOS, check /Applications for Adobe Acrobat or Adobe Acrobat Reader.
    Affected if The application is present on the system.
  2. Determine the installed version of Adobe Acrobat or Reader
    On Windows, right-click the executable (Acrobat.exe or AcroRd32.exe), select Properties, and view the Details tab for the Version field. Alternatively, open the application, go to Help > About Adobe Acrobat Reader to see the exact version number.
    Affected if A version is displayed that falls within the affected ranges.
  3. Compare installed version against affected ranges
    Match your installed version to these vulnerable ranges: Adobe Acrobat DC or Acrobat Reader DC versions 15.008.20082 through 26.001.21661 (for 26.x branch), and Adobe Acrobat versions 24.0.0 through 24.001.30382 (for 24.x branch).
    Affected if The installed version is greater than or equal to 15.008.20082 and less than 26.001.21662, OR greater than or equal to 24.0.0 and less than 24.001.30383.
  4. Verify PDF processing capability
    Confirm the application can open and render PDF files, as the vulnerability is triggered when a victim opens a maliciously crafted PDF file.
    Affected if The application is configured to open PDF files and has been used to process PDFs.

A user is affected if Adobe Acrobat or Acrobat Reader is installed with a version within the vulnerable ranges (15.008.20082 to 26.001.21661 for DC/Reader, or 24.0.0 to 24.001.30382 for Acrobat) and the application processes PDF files.

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 a version later than 26.001.21651 (or 24.001.30366+) to patch the vulnerability. Users should avoid opening untrusted PDF files until the update is applied.

Recommended fix High confidence

Acrobat Dc/Reader Dc: 26.001.21662 or later; Acrobat 24.x: 24.001.30383 or later

  1. 1. Identify the installed Adobe Acrobat/Reader product version from the Help > About menu
  2. 2. For Acrobat Dc or Acrobat Reader Dc: Download and install version 26.001.21662 or later from helpx.adobe.com
  3. 3. For Acrobat (24.x version): Download and install version 24.001.30383 or later from helpx.adobe.com
  4. 4. Restart the application after installation
  5. 5. Verify the installed version matches or exceeds the fixed release via Help > About

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

Fix this in Acrobat Dc Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-47921 — 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-47921 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