CVE-2026-47965
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 an out-of-bounds write 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 an out-of-bounds write vulnerability caused by improper bounds checking when parsing malformed PDF files. Successful exploitation allows arbitrary code execution in the context of the current user after the victim opens a 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>= 24.0.0, < 24.001.30365>= 15.008.20082, < 26.001.21651>= 15.008.20082, < 26.001.21651CVSS 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 Control Panel > Programs and Features, or run 'Get-WmiObject -Class Win32_Product | Select-Object Name, Version' in PowerShell to list installed Adobe productsAffected if No Adobe Acrobat or Reader products are found (not vulnerable)
-
Identify the installed Adobe product and versionOn Windows, check the version via the executable properties: right-click AcroRd32.exe or Acrobat.exe, select Properties > Details, or check registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Adobe Acrobat\[Version]Affected if The product name is Adobe Acrobat, Adobe Acrobat Dc, or Adobe Acrobat Reader Dc with a version that falls within the affected ranges
-
Compare Adobe Acrobat version 24.x against the affected rangeIf product is Adobe Acrobat version 24.x, verify the version is less than 24.001.30365. The full version number typically appears as 24.xxx.xxxxx in Help > About or the executable propertiesAffected if Version is 24.0.0 or higher but below 24.001.30365
-
Compare Adobe Acrobat Dc or Reader Dc against the affected rangeIf product is Adobe Acrobat Dc or Adobe Acrobat Reader Dc, verify the version falls between 15.008.20082 and 26.001.21650 inclusive. Check Help > About or the executable properties for the full version stringAffected if Version is 15.008.20082 or higher but below 26.001.21651
A user is affected if Adobe Acrobat (24.x line), Adobe Acrobat Dc, or Adobe Acrobat Reader Dc is installed with a version matching the specific affected ranges (24.0.0 to 24.001.30364, or 15.008.20082 to 26.001.21650) 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.3036526.001.21651
Update Acrobat Reader to version 24.001.30366 or later for the 24.x line, and 26.001.21652 or later for the 26.x line. Avoid opening untrusted PDF files from unknown sources until patches are applied.
Acrobat: 24.001.30365 or later | Acrobat Dc: 26.001.21651 or later | Acrobat Reader Dc: 26.001.21651 or later
- Navigate to helpx.adobe.com or the official Adobe Acrobat download page to obtain the latest version
- Download and install Adobe Acrobat version 24.001.30365 or later for the Acrobat product
- Download and install Adobe Acrobat Dc version 26.001.21651 or later for the Acrobat Dc product
- Download and install Adobe Acrobat Reader Dc version 26.001.21651 or later for the Acrobat Reader Dc product
- Verify the installed version by opening Adobe Acrobat/Reader, going to Help > About Adobe Acrobat/Reader, and confirming the version number meets the minimum fixed version
- Ensure all instances of Adobe Acrobat/Reader are closed before installing the update
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-47965 — 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-47965 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