CVE-2026-47916
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 · moderate confidenceUse After Free vulnerability in Adobe Acrobat Reader that allows arbitrary code execution when a victim opens a maliciously crafted PDF file. The vulnerability affects versions 24.001.30365, 26.001.21651 and earlier, requiring user interaction (opening a file) for exploitation.
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.
-
Locate installed Adobe Acrobat or Reader applicationOpen Adobe Acrobat/Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The version number is displayed in the dialog box.Affected if Application is Adobe Acrobat Dc, Adobe Acrobat Reader Dc, or Adobe Acrobat
-
Identify exact version number of Adobe Acrobat Dc or Reader DcIn the About dialog, note the full version number displayed (for example: 26.001.21651 or 24.001.30365). Compare against the affected range: versions 15.008.20082 through 26.001.21661 are vulnerable.Affected if Version is >= 15.008.20082 and < 26.001.21662 (for Dc variants)
-
Identify exact version number of Adobe Acrobat (classic)In the About dialog, note the full version number displayed. Compare against the affected range: versions 24.0.0 through 24.001.30382 are vulnerable.Affected if Version is >= 24.0.0 and < 24.001.30383 (for classic Acrobat)
-
Confirm the application processes PDF filesThis vulnerability is triggered when a user opens a specially crafted PDF file. Check whether the installed Adobe application is configured to open PDF documents.Affected if The application processes untrusted PDF files and the installed version falls within affected ranges
A user is affected if Adobe Acrobat Dc, Adobe Acrobat Reader Dc, or Adobe Acrobat is installed with a version matching the affected ranges and the application is used to open PDF files.
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 the latest patched version beyond 26.001.21651. Until patched, advise users to avoid opening PDF files from untrusted sources.
Acrobat DC/Reader DC: 26.001.21662 or later; Acrobat 24.x: 24.001.30383 or later
- Navigate to the official Adobe download page: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- For Acrobat DC/Reader DC: Download and install version 26.001.21662 or later
- For Acrobat (version 24.x): Download and install version 24.001.30383 or later
- Alternatively, use Adobe's Creative Cloud or standalone installer to update to the latest version
- Verify the installed version by opening Adobe Acrobat/Reader, going to Help > About Adobe Acrobat/Reader
- Ensure the version number meets or exceeds the minimum fixed version for your product (26.001.21662 for DC, 24.001.30383 for Acrobat 24.x)
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $2,752.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47916 — 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-47916 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