dbcve.org
AcrobatApplication · Adobe

CVE-2026-47912

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 versions prior to the fixed releases contain a Use After Free vulnerability. This memory corruption issue allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious PDF file.

MitigationUpdate Adobe Acrobat Reader to the latest patched version. Do not open untrusted PDF files from unknown sources.

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
AcrobatApplication
Affected:< 24.001.30383< 26.001.21662
Acrobat ReaderApplication
Affected:< 26.001.21662

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. Verify Adobe Acrobat Reader is installed
    On Windows, check for the application in Program Files/Adobe or look for acrord32.exe/acrodrdr.exe in the installation directory. On Mac, check /Applications for Adobe Acrobat Reader.
    Affected if The application must be present for exploitation to occur.
  2. Determine the installed version number
    Windows: Right-click the Adobe Acrobat Reader executable (acrord32.exe or AcroRd32.exe), select Properties, and view the Details tab for the Product Version. Alternatively, open the app and go to Help > About Adobe Acrobat Reader. Mac: Open the app and go to Adobe Acrobat Reader > About Adobe Acrobat Reader.
    Affected if Version cannot be determined if Reader is not installed.
  3. Compare against affected version ranges
    Compare your installed version to the following vulnerable ranges: versions earlier than 24.001.30383 (2024 track) OR versions earlier than 26.001.21662 (2025/2026 track). Any version matching these ranges is affected.
    Affected if Your installed version falls within the affected ranges: < 24.001.30383 or < 26.001.21662.
  4. Confirm user interaction requirement
    This vulnerability requires a user to open a specially crafted malicious PDF file. Check recent PDF opening activity from untrusted sources if compromise is suspected.
    Affected if The flaw is only exploitable when a victim opens a malicious PDF file.

You are affected if Adobe Acrobat Reader is installed and the version is earlier than 24.001.30383 or earlier than 26.001.21662, AND a user opens a 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 the latest patched version. Do not open untrusted PDF files from unknown sources.

Recommended fix High confidence

Acrobat: 24.001.30383 or higher, or 26.001.21662 or higher; Acrobat Reader: 26.001.21662 or higher

  1. 1. Ensure Adobe Acrobat or Acrobat Reader is completely closed before updating
  2. 2. Open Adobe Creative Cloud desktop application or navigate to the official Adobe Acrobat download page
  3. 3. Check for available updates or download the installer for the fixed version
  4. 4. For Acrobat: install version 24.001.30383 or higher, OR version 26.001.21662 or higher
  5. 5. For Acrobat Reader only: install version 26.001.21662 or higher
  6. 6. After installation, verify the version by opening the application and checking Help > About Adobe Acrobat/Reader

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

Fix this in Acrobat Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing2.0 h
  • Review / QA1.0 h
5.0 hours of engineering $860
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,376.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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