Application crash via malicious-file memory corruption
Published Aug 27, 2026 · Updated Aug 27, 2026
Out-of-bounds write in Adobe DNG SDK 1.7.1 2502 and earlier allows attackers to crash or hang applications via a malicious file. Adobe identifies memory corruption during malicious-file processing but has not published the affected parser, function, or unchecked write operation. Exploitation requires a victim to open the file; the reported consequence is an application crash or unresponsive state.
Summary
What happened
Out-of-bounds write in Adobe DNG SDK 1.7.1 2502 and earlier allows attackers to crash or hang applications via a malicious file. Adobe identifies memory corruption during malicious-file processing but has not published the affected parser, function, or unchecked write operation. Exploitation requires a victim to open the file; the reported consequence is an application crash or unresponsive state.
The record
- CVE
- CVE-2026-34620
- Published
- Aug 27, 2026
- Updated
- Aug 27, 2026
- Vendor
- Adobe
- Product
- Adobe DNG SDK
- Classifications
- CWE-787, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 27, 2026CVE publishedPublication date reported by the CVE source.
- Aug 27, 2026Record 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=0 <=1.7.1.2502
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.
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