CVE-2026-47955
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 · uneditedAcrobat 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 confidenceThis is a Use After Free (UAF) vulnerability in Adobe Acrobat Reader. Use After Free flaws occur when a program continues to use memory after it has been freed, potentially allowing an attacker to manipulate memory and achieve arbitrary code execution. The vulnerability is triggered when a victim opens a specially crafted malicious PDF file, and if successfully exploited, it executes code with the privileges of the current user.
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>= 15.008.20082, < 26.001.21662>= 15.008.20082, < 26.001.21662>= 24.0.0, < 24.001.30383CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Confirm Adobe Acrobat installationCheck if Adobe Acrobat or Adobe Acrobat Reader is installed on the system. On Windows, look in Program Files or check the registry under HKLM\SOFTWARE\Adobe. On macOS, check /Applications for Adobe Acrobat or Adobe Acrobat Reader.Affected if Adobe Acrobat or Adobe Acrobat Reader is installed
-
Determine installed version numberOpen Adobe Acrobat/Reader and navigate to Help > About Adobe Acrobat (or Reader). Alternatively, on Windows right-click the executable and select Properties > Details to view the File Version.Affected if The version displayed is 24.x or 26.x within the affected ranges (24.0.0 to 24.001.30383, or 15.008.20082 to 26.001.21651)
-
Compare against affected version rangesCompare your installed version against the known vulnerable ranges: Adobe Acrobat/Reader DC versions 15.008.20082 through 26.001.21651, or Adobe Acrobat versions 24.0.0 through 24.001.30383. Versions below 24.001.30365 or 26.001.21651 in these ranges are affected.Affected if Installed version falls within >= 15.008.20082 and < 26.001.21662 for DC products, or >= 24.0.0 and < 24.001.30383 for Acrobat
If Adobe Acrobat or Acrobat Reader DC is installed with a version between 15.008.20082 and 26.001.21651 (exclusive of 26.001.21662), or Acrobat version between 24.0.0 and 24.001.30383 (exclusive of 24.001.30383), the environment is affected by this UAF vulnerability.
Generated from the published advisory. Verify against your own configuration.
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 · scoped24.001.3038326.001.21662
Update Adobe Acrobat Reader to a version later than 26.001.21651 or 24.001.30365 (depending on the release track). Until patched, exercise caution when opening PDF files from untrusted sources, and consider enabling Adobe's Protected View or sandboxing features.
Acrobat DC/Reader DC: 26.001.21662 or later | Acrobat 2024: 24.001.30383 or later
- 1. Determine which Adobe Acrobat product is installed (Acrobat DC, Acrobat Reader DC, or Acrobat 2024/Classic)
- 2. For Acrobat DC / Acrobat Reader DC: Navigate to Help > Check for Updates and install version 26.001.21662 or later
- 3. Alternatively, download the latest version from the official Adobe Acrobat download page: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 4. Verify the installed version by going to Help > About Adobe Acrobat Reader/Acrobat
- 5. Ensure the version displayed is 26.001.21662 or higher for DC products, or 24.001.30383 or higher for Acrobat 2024
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,480.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47955 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-47955 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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