Arbitrary code execution via out-of-bounds write
Published Jun 10, 2025 · Updated Feb 26, 2026
Out-of-bounds write in Adobe InDesign ID20.2 and earlier and ID19.5.3 and earlier allows attackers to execute code through a malicious file. Adobe has not disclosed the affected parser, file format, or erroneous operation that writes beyond its allocated buffer. Exploitation requires a user to open the malicious file, after which code executes in the current user's context.
Summary
What happened
Out-of-bounds write in Adobe InDesign ID20.2 and earlier and ID19.5.3 and earlier allows attackers to execute code through a malicious file. Adobe has not disclosed the affected parser, file format, or erroneous operation that writes beyond its allocated buffer. Exploitation requires a user to open the malicious file, after which code executes in the current user's context.
The record
- CVE
- CVE-2025-43558
- Published
- Jun 10, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-787, T1204.002
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Jun 10, 2025CVE publishedPublication date reported by the CVE source.
- Feb 26, 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 <=ID19.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.
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