dbcve.org
AcrobatApplication · Adobe

CVE-2026-47959

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 Stack-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

A stack-based buffer overflow vulnerability exists in Adobe Acrobat Reader versions 24.001.30365, 26.001.21651 and earlier. When a user opens a maliciously crafted PDF file, the buffer overflow can be triggered, potentially allowing arbitrary code execution with the privileges of the current user.

MitigationApply the vendor-supplied security update from Adobe to the affected Acrobat Reader installations. Organizations should deploy patches through their enterprise patch management systems and ensure users do not open untrusted PDF files.

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. Check Adobe Acrobat Reader installed version
    Open Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader to display the version number. Alternatively, right-click the Acrobat Reader shortcut and select Properties to view the version information.
    Affected if The displayed version is 24.001.30365 or earlier, or 26.001.21651 or earlier, indicating the installed version is below the fixed releases (24.001.30383 and 26.001.21662).
  2. Compare version against CVE thresholds
    Compare your installed version number to the affected ranges: versions earlier than 24.001.30383 (for the 24.x branch) or earlier than 26.001.21662 (for the 26.x branch) are vulnerable.
    Affected if The installed version falls below 24.001.30383 or 26.001.21662, placing it within the vulnerable range.
  3. Verify if PDF files are handled by the application
    Confirm that Adobe Acrobat Reader is configured as the default application for opening PDF files, or that users in the environment commonly open PDF documents using this application.
    Affected if Adobe Acrobat Reader is the default PDF handler or is regularly used to open PDF files, enabling the attack surface.

A user is affected if their installed Adobe Acrobat Reader version is below 24.001.30383 or 26.001.21662 and they open PDF files with the application.

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

Apply the vendor-supplied security update from Adobe to the affected Acrobat Reader installations. Organizations should deploy patches through their enterprise patch management systems and ensure users do not open untrusted PDF files.

Recommended fix High confidence

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

  1. 1. Identify whether Acrobat or Acrobat Reader is installed by opening the application and navigating to Help > About Adobe Acrobat (or Reader)
  2. 2. Note the current version number
  3. 3. For Acrobat: upgrade to version 24.001.30383 or later, OR upgrade to version 26.001.21662 or later
  4. 4. For Acrobat Reader only: upgrade to version 26.001.21662 or later
  5. 5. Download the updated version from the official Adobe website at helpx.adobe.com
  6. 6. Run the installer and follow the prompts to complete the upgrade
  7. 7. After installation, verify the new version by checking Help > About again to confirm the version meets the minimum fixed release
  8. 8. Ensure user interaction is minimized by warning users not to open untrusted PDF files
Caveat Upgrading to a newer major version (e.g., from version 24 to 26) may introduce user interface changes; ensure compatibility with existing workflows

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

Fix this in Acrobat 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-47959 — 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-47959 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