CVE-2026-47918
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 confidenceA Use After Free vulnerability exists in Adobe Acrobat Reader versions 24.001.30365, 26.001.21651 and earlier. The vulnerability allows arbitrary code execution in the context of the current user when a victim opens a specially crafted malicious PDF file.
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.
-
Identify installed Adobe productCheck Add/Remove Programs or the program folder for Adobe Acrobat DC, Adobe Acrobat Reader DC, or Adobe Acrobat. Look for the product name in the Start Menu or Program Files.Affected if Any of these three Adobe products are installed
-
Check Adobe Acrobat DC versionOpen Adobe Acrobat DC, go to Help > About Adobe Acrobat DC, or right-click the executable in Program Files\Adobe\Acrobat DC\Acrobat\Acrobat.exe and select Properties > Details to view the Product Version.Affected if Version is >= 15.008.20082 and < 26.001.21662
-
Check Adobe Acrobat Reader DC versionOpen Adobe Acrobat Reader DC, go to Help > About Adobe Acrobat Reader DC, or right-click the executable in Program Files\Adobe\Acrobat Reader DC\Reader\AcroRd32.exe and select Properties > Details to view the Product Version.Affected if Version is >= 15.008.20082 and < 26.001.21662
-
Check Adobe Acrobat versionOpen Adobe Acrobat (classic), go to Help > About Adobe Acrobat, or right-click the executable in Program Files\Adobe\Acrobat [version]\Acrobat\Acrobat.exe and select Properties > Details to view the Product Version.Affected if Version is >= 24.0.0 and < 24.001.30383
You are affected if you have Adobe Acrobat DC, Reader DC, or Adobe Acrobat installed and the installed version falls within the affected ranges listed above.
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. Avoid opening PDF files from untrusted or unknown sources.
Acrobat 24.001.30383 or Acrobat DC/Reader DC 26.001.21662
- 1. Determine which Adobe Acrobat product is installed (Acrobat, Acrobat DC, or Acrobat Reader DC)
- 2. For Acrobat (classic): upgrade to version 24.001.30383 or later
- 3. For Acrobat DC or Acrobat Reader DC: upgrade to version 26.001.21662 or later
- 4. Download the appropriate update from the official Adobe website (helpx.adobe.com)
- 5. Run the installer and follow the prompts to complete the upgrade
- 6. Restart the application after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47918 — 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-47918 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