CVE-2026-47917
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 confidenceAdobe Acrobat Reader contains a Use After Free vulnerability where the application attempts to use memory that has already been freed, potentially allowing arbitrary code execution in the context of the current user when a malicious PDF file is opened.
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.
-
Check if Adobe Acrobat or Reader is installedOn Windows, open Programs and Features or check registry key HKLM\SOFTWARE\Adobe. On macOS, check /Applications for Adobe Acrobat or Adobe Reader. Also check Start menu shortcuts.Affected if Adobe Acrobat Dc, Adobe Acrobat Reader Dc, or Adobe Acrobat is present on the system
-
Identify the installed version numberOn Windows: Right-click the application in Programs and Features and select Properties, then view the Version field. Or open the application, go to Help > About Adobe Acrobat/Reader. On macOS: Right-click the app in Applications > Get Info.Affected if The version shown is 26.001.21651 or earlier, or 24.001.30365 or earlier (for the 24.x track), or any version from 15.008.20082 up to the patched versions
-
Compare version against affected rangesMatch your installed version to these ranges: Acrobat Dc/Reader Dc: 15.008.20082 through 26.001.21661 are affected; Acrobat (24.x): 24.0.0 through 24.001.30382 are affected. Versions below 15.008.20082 are not in scope.Affected if Your version falls within any of these ranges: 15.008.20082 to 26.001.21661 for Acrobat Dc/Reader Dc, or 24.0.0 to 24.001.30382 for Acrobat 24.x
-
Determine if PDF files can be opened by the applicationVerify that the PDF open action is associated with the installed Adobe application. Check default file associations in Windows (Settings > Apps > Default Apps > Choose default apps by file type) or on macOS (right-click any PDF > Get Info > Open with).Affected if PDF files are set to open automatically with the vulnerable Adobe application, increasing exposure to malicious PDFs
If Adobe Acrobat Dc, Acrobat Reader Dc, or Acrobat (24.x) is installed and its version falls within 15.008.20082-26.001.21661 (for DC products) or 24.0.0-24.001.30382 (for Acrobat 24.x), the environment is affected.
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 newer than 24.001.30365 and 26.001.21651 to remediate this vulnerability.
Acrobat DC/Reader DC: 26.001.21662 or later; Acrobat (classic): 24.001.30383 or later
- Navigate to the Adobe Acrobat download page at helpx.adobe.com/acrobat/download.html
- Identify your installed Acrobat product (Acrobat DC, Acrobat Reader DC, or Acrobat)
- For Acrobat DC and Acrobat Reader DC: Download and install version 26.001.21662 or later
- For Acrobat (classic): Download and install version 24.001.30383 or later
- Alternatively, use Adobe's automatic update feature by opening Acrobat/Reader, going to Help > Check for Updates
- Follow the on-screen prompts to complete the installation
- Restart the application after the update completes
- Verify the installed version by going to Help > About Adobe Acrobat [Reader]
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-47917 — 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-47917 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