dbcve.org
AcrobatApplication · Adobe

CVE-2026-34622

HIGH · 8.6 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 24.001.30365 / 26.001.21431 or later.
See remediation →
89/100
Remediation priority · High
No privileges

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 · unedited
Acrobat 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 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 confidence

Adobe Acrobat Reader contains a Prototype Pollution vulnerability where improper controls allow modification of object prototype attributes. This can be exploited by having a victim open a malicious PDF file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate Adobe Acrobat Reader to a version later than 26.001.21411, 24.001.30360, or 24.001.30362. Additionally, train users to avoid opening untrusted PDF files.

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
AcrobatApplication
Affected:>= 24.0.0, < 24.001.30365
Acrobat DcApplication
Affected:>= 15.008.20082, < 26.001.21431
Acrobat Reader DcApplication
Affected:>= 15.008.20082, < 26.001.21431

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify the installed Adobe product
    Open Adobe Acrobat or Adobe Acrobat Reader, then go to Help > About Adobe Acrobat Reader (or About Adobe Acrobat). The product name (Acrobat, Acrobat DC, or Acrobat Reader DC) appears in the title bar or about dialog.
    Affected if The installed product is Adobe Acrobat, Adobe Acrobat DC, or Adobe Acrobat Reader DC.
  2. Determine the installed version number
    In the About dialog, note the full version number displayed (for example: 24.001.30360 or 15.008.20082). Record this exact version string.
    Affected if A version number is displayed.
  3. Compare version against affected ranges
    Compare your installed version to these affected ranges: Adobe Acrobat versions 24.0.0 through 24.001.30364; Adobe Acrobat DC versions 15.008.20082 through 26.001.21430; Adobe Acrobat Reader DC versions 15.008.20082 through 26.001.21430. If your version falls within any of these ranges, the vulnerability is present.
    Affected if Your version is >= 24.0.0 and < 24.001.30365 (for Acrobat), OR >= 15.008.20082 and < 26.001.21431 (for Acrobat DC/Reader DC).
  4. Verify if the JavaScript port is enabled
    In Adobe Reader/Acrobat, go to Edit > Preferences > Security (or Trust Manager) and check if the JavaScript port or JavaScript execution is enabled. Alternatively, open the Registry key (if on Windows) at HKEY_CURRENT_USER\Software\Adobe\Acrobat Reader\[version]\FeatureState and look for JavaScript-related entries.
    Affected if JavaScript is enabled in the Reader/Acrobat security settings.

You are affected if you have Adobe Acrobat, Acrobat DC, or Acrobat Reader DC installed with a version matching the affected ranges AND the product has JavaScript enabled, allowing malicious PDFs to execute code.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 24.001.30365 / 26.001.21431 or later
Fixed in 24.001.3036526.001.21431
Interim mitigation

Update Adobe Acrobat Reader to a version later than 26.001.21411, 24.001.30360, or 24.001.30362. Additionally, train users to avoid opening untrusted PDF files.

Recommended fix High confidence

Acrobat 24.x -> 24.001.30365 or later; Acrobat Dc/Acrobat Reader Dc -> 26.001.21431 or later

  1. 1. Open Adobe Acrobat or Acrobat Reader on your system
  2. 2. Navigate to Help > Check for Updates (or use the Help menu)
  3. 3. If an update is available, download and install the latest version
  4. 4. Alternatively, download the fixed version directly from adobe.com: For Acrobat 24.x use version 24.001.30365 or later; For Acrobat Dc/Acrobat Reader Dc use version 26.001.21431 or later
  5. 5. Restart the application after the update completes
  6. 6. Verify the version by going to Help > About Adobe Acrobat/Reader to confirm the installed version

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Acrobat Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34622 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34622 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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