CVE-2026-47914
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 (UAF) memory corruption vulnerability in 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, requiring user interaction 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< 24.001.30383< 26.001.21662< 26.001.21662CVSS 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 Reader is installedCheck the system for Adobe Acrobat Reader installation. On Windows, look in C:\Program Files\Adobe\Acrobat or C:\Program Files (x86)\Adobe\Acrobat. On macOS, check /Applications for Adobe Acrobat Reader. Alternatively, check Windows Registry key HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\{AC76BA86-7AD7-xxxx-xxxx-xxxxxxxxxxxx}Affected if Adobe Acrobat Reader is not installed on the system
-
Identify the installed versionLocate the Adobe Acrobat Reader executable (e.g., AcroRd32.exe or Adobe Acrobat Reader.exe) and view its properties to see the File Version. On Windows, right-click the executable, select Properties, and check the Details tab. On macOS, right-click the app in Applications, select Get Info, and check the Version field.Affected if Unable to determine the installed version number
-
Compare version to affected rangesCompare your installed version to the affected version thresholds: Adobe Acrobat Reader versions below 26.001.21662 are vulnerable. If your version starts with 24.x, versions below 24.001.30383 are also affected.Affected if The installed version is below 26.001.21662 (or below 24.001.30383 for the 24.x track)
-
Determine exposure to malicious PDF filesAssess whether users in the environment commonly open PDF files from untrusted or unknown sources. The vulnerability is triggered when a victim opens a malicious PDF file.Affected if Users routinely open PDF attachments from untrusted or unknown sources while using a vulnerable version
A user is affected if Adobe Acrobat Reader version is below 26.001.21662 AND the user opens PDF files from untrusted sources.
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 version 26.001.21652 or later (for branch 26) and 24.001.30366 or later (for branch 24) to address the UAF vulnerability. Users should avoid opening untrusted PDF files until updates are applied.
Acrobat 24.001.30383+ or 26.001.21662+; Acrobat Reader 26.001.21662+
- 1. Determine current Adobe Acrobat or Acrobat Reader version by opening the application, selecting Help > About Adobe Acrobat (or About Adobe Acrobat Reader)
- 2. If running version 24.x branch: upgrade to version 24.001.30383 or later
- 3. If running version 26.x branch: upgrade to version 26.001.21662 or later
- 4. Download the fixed version from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 5. Close all running instances of Adobe Acrobat or Acrobat Reader
- 6. Run the installer and follow the on-screen prompts to complete the upgrade
- 7. Verify the installed version matches or exceeds the fixed release numbers after installation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.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 $1,376.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47914 — 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-47914 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