Code execution via malicious file heap overflow
Published Jun 9, 2026 · Updated Jun 9, 2026
Heap-based buffer overflow in Adobe InDesign 21.3 and earlier and 20.5.3 and earlier allows attackers to execute code through a malicious file. Adobe discloses no affected parser, file format, or specific memory-copy operation, so the precise code locus and unchecked input operation remain undisclosed. Exploitation requires a user to open the file, after which code runs in the context of that user on Windows or macOS.
Summary
What happened
Heap-based buffer overflow in Adobe InDesign 21.3 and earlier and 20.5.3 and earlier allows attackers to execute code through a malicious file. Adobe discloses no affected parser, file format, or specific memory-copy operation, so the precise code locus and unchecked input operation remain undisclosed. Exploitation requires a user to open the file, after which code runs in the context of that user on Windows or macOS.
The record
- CVE
- CVE-2026-34698
- Published
- Jun 9, 2026
- Updated
- Jun 9, 2026
- Vendor
- Adobe
- Product
- Adobe InDesign
- Classifications
- CWE-122, T1204.002, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 9, 2026CVE publishedPublication date reported by the CVE source.
- Jun 9, 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 <=20.5.3
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