CVE-2026-34621
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.30356, 26.001.21367 and earlier are affected by an Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') 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 Prototype Pollution vulnerability where improper controls on object prototype attribute modification could allow an attacker to execute arbitrary code in the context of the current user. The attack requires the victim to open 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< 26.001.21411< 26.001.21411>= 24.0.0, < 24.001.30362>= 24.0.0, < 24.001.30360CVSS 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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/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 installed Adobe Acrobat Reader version on WindowsOpen Registry Editor and navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\Acrobat Reader\DC\Version (or Acrobat\DC\Version for full Acrobat). The default value displays the installed version number.Affected if The installed version is less than 24.001.30360 (for 24.x releases) or less than 26.001.21411 (for 26.x releases)
-
Check Adobe Acrobat version via application UIOpen Adobe Acrobat Reader or Acrobat, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The version number appears in the dialog that opens.Affected if The displayed version matches the affected ranges: any 24.x version below 24.001.30360/24.001.30362, or any 26.x version below 26.001.21411
-
Identify product variant (Reader vs full Acrobat)Check the registry key path or application name. Reader uses 'Acrobat Reader' in the path, while full Acrobat uses just 'Acrobat'. Also visible in the application title bar.Affected if The installed product is Adobe Acrobat Reader DC or Adobe Acrobat DC and the version falls within affected ranges
-
Determine if JavaScript is enabled in PDF settingsIn Adobe Acrobat/Reader, go to Edit > Preferences > JavaScript. Verify if 'Enable Adobe JavaScript' is checked.Affected if JavaScript is enabled AND the installed version is within the affected version ranges, as the exploitation requires JavaScript execution to achieve arbitrary code execution
A user is affected if Adobe Acrobat Reader DC or Adobe Acrobat DC is installed with a version below 24.001.30360 (for 24.x) or below 26.001.21411 (for 26.x), particularly when 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.3036024.001.3036226.001.21411
Update Adobe Acrobat Reader to a version later than 26.001.21367 (or 24.001.30356) and avoid opening untrusted or unsolicited PDF files.
Acrobat/Acrobat Reader 24.001.30360+ (24.x line) or 26.001.21411+ (26.x line)
- 1. Open Adobe Acrobat or Adobe Acrobat Reader on your system
- 2. Navigate to Help > Check for Updates (or use the menu specific to your OS)
- 3. Allow the application to check for and download available updates
- 4. Install the latest version when prompted, or manually download from the official Adobe website at https://get.adobe.com/reader/ (for Reader) or https://get.adobe.com/acrobat/ (for Acrobat)
- 5. Verify the installed version by going to Help > About Adobe Acrobat (or About Adobe Acrobat Reader)
- 6. Confirm the version number matches or exceeds the fixed release: 24.001.30360 or later for version 24.x, or 26.001.21411 or later for version 26.x
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34621 — 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-34621 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