Cyber Resilience

CVE-2026-34626

Adobe Acrobat 24.0.0 – 24.001.30365

Published
14 April 2026
Modified
16 April 2026
Patch / advisory
View advisory
CVSS Score v3.1 6.3
Click a component to see what it means
Raw vectorCVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:C/C:H/I:N/A:N
EPSS Score 0.0034 26th percentile
Risk Priority 35 floored blend · peak EPSS

Summary

CVE-2026-34626 is a medium-severity Prototype Pollution (CWE-1321) vulnerability in Adobe Acrobat. Its CVSS base score is 6.3 (Medium).

Operationally, exploitation aligns with the MITRE ATT&CK technique Malicious File (T1204.002); ranked at the 26th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.

The strongest mitigations our analysis identified map to SI-2 (Flaw Remediation) and AC-6 (Least Privilege) — see the control section below for these in your framework.

EU & UK References

Vulnerability Data

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 file system read in the context of the current user. Exploitation of this…

more

issue requires user interaction in that a victim must open a malicious file.

CWE(s)
CWE-1321

Related Threats

MITRE ATT&CK Enterprise TechniquesAI

T1204.002 Malicious File Execution
An adversary may rely upon a user opening a malicious file in order to gain execution.
attack.mitre.org →
T1005 Data from Local System Collection
Adversaries may search local system sources, such as file systems, configuration files, local databases, virtual machine files, or process memory, to find files of interest and sensitive data prior to Exfiltration.
attack.mitre.org →
Why these techniques?

Malicious file delivery for user execution combined with arbitrary local file read capability.

Confidence: MEDIUM · MITRE ATT&CK Enterprise v19.0

CVEs Like This One

CVE-2026-34622Same product: Adobe Acrobat
CVE-2026-34621Same product: Adobe Acrobat
CVE-2026-47923Same product: Adobe Acrobat
CVE-2026-47924Same product: Adobe Acrobat
CVE-2026-47919Same product: Adobe Acrobat
CVE-2026-47926Same product: Adobe Acrobat
CVE-2026-47918Same product: Adobe Acrobat
CVE-2026-47955Same product: Adobe Acrobat
CVE-2026-47915Same product: Adobe Acrobat
CVE-2026-47965Same product: Adobe Acrobat

Affected Assets

adobe
acrobat
24.0.0 — 24.001.30365
adobe
acrobat dc
15.008.20082 — 26.001.21431
adobe
acrobat reader dc
15.008.20082 — 26.001.21431

Mitigating Controls

Control response

Prevent
Stop it (NIST 800-53)
  • SI-2 Flaw Remediation
  • CM-7 Least Functionality
  • AC-6 Least Privilege
Detect
Catch it (NIST detect / respond)

—

Harden
Shrink the surface (DISA STIG)

—

Validate
Prove the fix (OWASP ASVS)
  • V15.3.6

Mitigating Controls (NIST 800-53 r5) AI

SI-2 Flaw Remediation good match
prevent

Directly requires timely installation of vendor patches that remediate the prototype-pollution flaw in the listed Acrobat Reader versions.

CM-7 Least Functionality partial match
prevent

Enforces disabling Acrobat JavaScript and other non-essential processing features that are the attack vector for the malicious PDF.

AC-6 Least Privilege partial match
prevent

Limits the impact of a successful file-system read by constraining the privileges of the Acrobat Reader process or user account.

Mitigating Controls (NIST CSF 2.0) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.

PR.PS-06 mostly match
prevents

Secure SDLC practices directly require input validation and safe property assignment to prevent prototype pollution.

Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI

Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.

A.8.29 Security testing in development and acceptance mostly match
detects

Security testing in development catches prototype-pollution flaws before release.

A.8.25 Secure development life cycle partial match
prevents

Secure development lifecycle mandates input validation and object-handling controls that directly prevent prototype pollution.

A.8.26 Application security requirements partial match
prevents

Application security requirements explicitly call for safeguards against unsafe object attribute manipulation.

A.8.27 Secure system architecture and engineering principles partial match
prevents

Secure architecture principles reduce the likelihood of prototype pollution through safe design patterns.

A.8.28 Secure coding partial match
prevents

Secure coding standards directly prohibit unsafe prototype attribute assignment and require defensive checks.

A.8.32 Change management partial match
prevents

Change-management processes ensure security fixes for prototype-pollution issues are tracked and deployed.

References