Code execution via malicious file use-after-free
Published Aug 12, 2025 · Updated Feb 26, 2026
Use-after-free in Adobe InCopy 20.4, 19.5.4 and earlier allows attackers to execute arbitrary code when a user opens a malicious file. Adobe identifies use of memory after it is freed but has not disclosed the affected component, object type, or triggering file structure. Execution occurs with the current user's privileges and depends on convincing that user to open the crafted file; no network service is implicated.
Summary
What happened
Use-after-free in Adobe InCopy 20.4, 19.5.4 and earlier allows attackers to execute arbitrary code when a user opens a malicious file. Adobe identifies use of memory after it is freed but has not disclosed the affected component, object type, or triggering file structure. Execution occurs with the current user's privileges and depends on convincing that user to open the crafted file; no network service is implicated.
The record
- CVE
- CVE-2025-54223
- Published
- Aug 12, 2025
- Updated
- Feb 26, 2026
- Vendor
- Adobe
- Product
- InCopy
- Classifications
- CWE-416, T1204.002, 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.
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