PatchSiren cyber security CVE debrief
CVE-2026-34626 Adobe CVE debrief
AI-assisted PatchSiren debrief based on the supplied source corpus. The CVE record was published on 2026-04-14T17:16:51.283Z and has not been modified since then. The CVE-2026-34626 vulnerability is an Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') issue affecting Adobe Acrobat Reader. This vulnerability could result in arbitrary file system read in the context of the current user when a victim opens a malicious file. The CVSS score for this vulnerability is 6.3, indicating a medium severity level. Organizations and individuals using Adobe Acrobat Reader versions 26.001.21411, 24.001.30360, 24.001.30362, and earlier should be aware of this vulnerability and take necessary defensive actions to prevent exploitation.
- Vendor
- Adobe
- Product
- Acrobat DC
- CVSS
- MEDIUM 6.3
- CISA KEV
- Not listed in stored evidence
- Original CVE published
- 2026-04-14
- Original CVE updated
- 2026-08-28
- Advisory published
- 2026-04-14
- Advisory updated
- 2026-08-28
Who should care
Organizations and individuals using Adobe Acrobat Reader versions 26.001.21411, 24.001.30360, 24.001.30362, and earlier should be aware of this vulnerability and take necessary defensive actions to prevent exploitation.
Technical summary
The CVE-2026-34626 vulnerability is an Improperly Controlled Modification of Object Prototype Attributes ('Prototype Pollution') issue affecting Adobe Acrobat Reader. This vulnerability could result in arbitrary file system read in the context of the current user when a victim opens a malicious file. The CVSS score for this vulnerability is 6.3, indicating a medium severity level. The vulnerability affects Adobe Acrobat Reader versions 26.001.21411, 24.001.30360, 24.001.30362, and earlier. Evidence is based on official CVE Program and NVD records. To address this vulnerability, it is recommended to apply vendor patches or updates as recommended by Adobe, monitor user interactions with files, especially malicious files, to prevent exploitation, and implement compensating controls, such as restricting file system access, if patching is not immediately feasible.
Defensive priority
Medium-priority defensive actions are recommended due to the CVSS score of 6.3 and the potential for arbitrary file system read in the context of the current user.
Recommended defensive actions
- Inventory and verify Adobe Acrobat Reader versions 26.001.21411, 24.001.30360, 24.001.30362, and earlier for potential vulnerability.
- Apply vendor patches or updates as recommended by Adobe.
- Monitor user interactions with files, especially malicious files, to prevent exploitation.
- Implement compensating controls, such as restricting file system access, if patching is not immediately feasible.
- Educate users about the risks of opening malicious files and the importance of keeping software up-to-date.
Evidence notes
The CVE-2026-34626 vulnerability affects Adobe Acrobat Reader versions 26.001.21411, 24.001.30360, 24.001.30362, and earlier, allowing for arbitrary file system read in the context of the current user upon opening a malicious file. Evidence is based on official CVE Program and NVD records.
Sources and references
Verified primary and authoritative sources
-
CVE-2026-34626 CVE Program record
Publisher, destination, and source semantics verified
URL: https://www.cve.org/CVERecord?id=CVE-2026-34626
CVE Program - Official CVE Program record with source-provided CVE metadata.
-
CVE-2026-34626 NVD vulnerability detail
Publisher, destination, and source semantics verified
URL: https://nvd.nist.gov/vuln/detail/CVE-2026-34626
NIST National Vulnerability Database - Official NIST NVD detail page and source-specific vulnerability assessment.
Supplemental references
-
Source reference
Unverified legacy reference
URL: https://helpx.adobe.com/security/products/acrobat/apsb26-44.html
[email protected] - Vendor Advisory
Methodology and review provenance
AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.