Code execution via out-of-bounds write
Published Apr 12, 2023 · Updated Mar 5, 2025
Out-of-bounds write in Adobe Acrobat Reader allows attackers to execute code in the current user's context via a malicious file. Adobe has not disclosed the affected parsing component, unchecked value, or memory operation that writes beyond its intended buffer. Affected releases are 23.001.20093 and earlier on Continuous and 20.005.30441 and earlier on Classic 2020; exploitation requires a victim to open the file.
Summary
What happened
Out-of-bounds write in Adobe Acrobat Reader allows attackers to execute code in the current user's context via a malicious file. Adobe has not disclosed the affected parsing component, unchecked value, or memory operation that writes beyond its intended buffer. Affected releases are 23.001.20093 and earlier on Continuous and 20.005.30441 and earlier on Classic 2020; exploitation requires a victim to open the file.
The record
- CVE
- CVE-2023-26395
- Published
- Apr 12, 2023
- Updated
- Mar 5, 2025
- Vendor
- Adobe
- Product
- Adobe Acrobat Reader
- Classifications
- CWE-787, T1203, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Apr 12, 2023CVE publishedPublication date reported by the CVE source.
- Mar 5, 2025Record updatedLatest update available in the CVE record.
Exploitability
Present is not the same as exploitable
Compare your product and version with the public record. A matching version still requires validation against your environment.
Is a vulnerable build present?
Compare these published version ranges with your installed build and any vendor patches.
- Affected versionversion=unspecified <=20.005.30441
- Affected versionversion=unspecified <=23.001.20093
- Affected versionversion=unspecified <=None
What conditions does exploitation require?
What is affected?
Published CVSS scores
CVSS describes severity. EPSS estimates exploitation probability.
Attacks
What attackers are doing with it
Daily unique IPs observed by Shadowserver honeypots for known exploited vulnerabilities (KEVs). Missing observations do not establish an absence of attacks.
Weakness, pattern, technique
Public exploit references
No public exploit references are available in this record.
Labels summarize the accepted research assessment. They do not indicate a test against your environment.
Technologies
Your stack
See the directory against your own environment.
Your stack
Check the software in your environment
Book a demo to see how Hinoki identifies affected software and validates exploitability in your environment.
Book a demo