CVE-2026-27287
Out-of-Bounds Read in Adobe InCopy Enables Code Execution
Publication date: 2026-04-14
Last updated on: 2026-04-15
Assigner: Adobe Systems Incorporated
Description
Description
CVSS Scores
EPSS Scores
| Probability: | |
| Percentile: |
Meta Information
Affected Vendors & Products
| Vendor | Product | Version / Range |
|---|---|---|
| adobe | incopy | to 20.5.3 (exc) |
| adobe | incopy | From 21.0 (inc) to 21.3 (exc) |
Helpful Resources
Exploitability
| CWE ID | Description |
|---|---|
| CWE-125 | The product reads data past the end, or before the beginning, of the intended buffer. |
Attack-Flow Graph
AI Powered Q&A
Can you explain this vulnerability to me?
This vulnerability affects Adobe InCopy versions 20.5.2, 21.2, and earlier. It is an out-of-bounds read issue that occurs when the software parses a specially crafted file. This flaw can cause the program to read beyond the end of an allocated memory structure.
An attacker could exploit this vulnerability by convincing a user to open a malicious file, which could then allow the attacker to execute code with the same privileges as the current user.
How can this vulnerability impact me? :
If exploited, this vulnerability can lead to arbitrary code execution in the context of the current user. This means an attacker could potentially run malicious code on your system, leading to unauthorized actions such as data theft, system compromise, or further malware installation.
Exploitation requires user interaction, specifically opening a malicious file, so the risk depends on user behavior and exposure to untrusted files.
What immediate steps should I take to mitigate this vulnerability?
To mitigate this vulnerability, avoid opening files from untrusted or unknown sources in affected versions of Adobe InCopy (20.5.2, 21.2 and earlier).
Since exploitation requires user interaction by opening a crafted malicious file, educating users to be cautious about opening unexpected or suspicious files can reduce risk.
Additionally, updating Adobe InCopy to a version later than 21.2 when a patch is available will address the vulnerability.