Code execution via heap overflow during file parsing
Published Aug 12, 2025 · Updated Feb 26, 2026
Heap-based buffer overflow in Adobe InDesign 20.4, 19.5.4 and earlier allows attackers to execute code via a malicious file. Adobe identifies the failure only as a heap-based buffer overflow during malicious-file processing and has not disclosed the affected parser, file format, or faulty bounds operation. Exploitation requires a user to open the file, after which code runs with that user's privileges and can compromise the user session.
Summary
What happened
Heap-based buffer overflow in Adobe InDesign 20.4, 19.5.4 and earlier allows attackers to execute code via a malicious file. Adobe identifies the failure only as a heap-based buffer overflow during malicious-file processing and has not disclosed the affected parser, file format, or faulty bounds operation. Exploitation requires a user to open the file, after which code runs with that user's privileges and can compromise the user session.
The record
- CVE
- CVE-2025-54211
- Published
- Aug 12, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- InDesign
- Classifications
- CWE-122, T1203
- Attack vector
- local
- Privileges
- unauthenticated
Timeline
How it unfolded
- Aug 12, 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 <=19.5.4
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