CVE-2026-34626
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 26.001.21411, 24.001.30360, 24.001.30362 and earlier are affected by an Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') vulnerability that could result in arbitrary file system read 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 Prototype Pollution vulnerability where improper control of object prototype attributes allows a specially crafted PDF to trigger arbitrary file system read operations in the context of the current user. This JavaScript-based vulnerability in the PDF rendering engine is triggered when a 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.21431>= 15.008.20082, < 26.001.21431CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
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 Adobe Acrobat Reader versionOpen Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader (or press Ctrl+Alt+A). The version number will be displayed in the dialog box.Affected if The installed version is 24.0.0 or higher but lower than 24.001.30365, OR 15.008.20082 or higher but lower than 26.001.21431.
-
Identify the specific product variantCheck the About dialog to determine if you are using 'Adobe Acrobat Reader DC' or another variant. The product name appears in the title bar of the About window.Affected if The product is Adobe Acrobat Reader DC with version 15.008.20082 or higher but lower than 26.001.21431, or standard Adobe Acrobat version 24.0.0 or higher but lower than 24.001.30365.
-
Confirm JavaScript execution is enabled for PDFsIn Adobe Acrobat Reader, go to Edit > Preferences > JavaScript. Verify if the 'Enable Adobe JavaScript' option is checked.Affected if JavaScript is enabled. The vulnerability requires JavaScript to be executed within the PDF rendering engine to trigger the prototype pollution.
-
Check for recent PDF handling behaviorReview recent PDF files opened on the system, particularly any unexpected file access operations or alerts from security software related to PDF file system access.Affected if Untrusted or suspicious PDF files were opened recently, as the attack requires a specially crafted malicious PDF.
You are affected if your Adobe Acrobat Reader version falls within the listed vulnerable ranges AND JavaScript execution is enabled in the application settings.
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.21431
Update Adobe Acrobat Reader to the latest version provided by Adobe. Until patched, exercise caution when opening PDF files from untrusted sources.
Acrobat 24.001.30365+ | Acrobat DC 26.001.21431+ | Acrobat Reader DC 26.001.21431+
- 1. Identify the exact Adobe Acrobat or Acrobat Reader product installed (Acrobat Standard, Acrobat Pro, or Acrobat Reader DC).
- 2. For Adobe Acrobat: Navigate to Help > Check for Updates and install version 24.001.30365 or later.
- 3. For Adobe Acrobat DC (Standard/Pro): Navigate to Help > Check for Updates and install version 26.001.21431 or later.
- 4. For Adobe Acrobat Reader DC: Navigate to Help > Check for Updates and install version 26.001.21431 or later.
- 5. Alternatively, download the latest version directly from the official Adobe website: https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat).
- 6. Verify the installed version by going to Help > About Adobe Acrobat [Product] and confirm the version meets or exceeds the minimum fixed version for your product.
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34626 — 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-34626 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