InCopy versions 20.5.2, 21.2 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code in the context of the current user. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Security readout for executives and security teams
Plain-English summary
Adobe InCopy can be compromised when a user opens a specially crafted file. Successful exploitation could let an attacker run code with that user’s permissions, potentially exposing data, altering files, or disrupting the workstation.
Executive priority
Treat this as a high-priority workstation remediation issue, especially for publishing and content teams handling external files. Schedule prompt patching and reinforce malicious-file controls; emergency incident response is not indicated solely by the supplied exploitation evidence.
Technical view
CVE-2026-27287 is a CWE-125 out-of-bounds read in InCopy’s file parsing. Reading beyond an allocated memory structure may lead to code execution as the current user. CVSS 3.1 rates it 7.8: local delivery, low complexity, no privileges required, and user interaction required.
Likely exposure
Workstations using InCopy 20.5.2, 21.2, or earlier listed versions are potentially exposed, particularly where users receive or open files from external or untrusted sources. The supplied version data should be reconciled with Adobe advisory APSB26-33.
Exploitation context
Exploitation requires convincing a victim to open a malicious file. The supplied bundle marks the CVE as absent from KEV and provides no evidence of active exploitation. That absence does not establish that exploitation is impossible or unobserved elsewhere.
Researcher notes
The source bundle identifies an out-of-bounds read during crafted-file parsing but does not provide the affected parser, file format, root cause, public proof of concept, or observed exploitation. Avoid assuming that the CWE alone explains how code execution occurs. Validate version ranges directly against APSB26-33.
Mitigation direction
Follow Adobe advisory APSB26-33 and upgrade affected InCopy installations to the vendor-designated corrected release.
Prioritize systems whose users routinely process files received from customers, contractors, email, or shared repositories.
Until updated, restrict opening unsolicited InCopy-compatible files and route suspicious documents through established security review.
Apply least privilege so successful code execution has reduced access to business data and system resources.
Validation and detection
Inventory installed InCopy versions and compare each installation with the affected versions and Adobe advisory.
Confirm updated endpoints report the vendor-designated corrected version through endpoint or software-management tooling.
Review endpoint telemetry for unusual child processes or file activity following InCopy document openings.
Test organizational controls for quarantining or warning users about unsolicited files handled by InCopy.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
1CVSS vectors
3Timeline events
1ADP providers
2Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
1 official score
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.