InDesign Desktop versions 20.5.2, 21.2 and earlier are affected by an out-of-bounds write vulnerability that could result in arbitrary code execution 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
A malicious InDesign document can corrupt memory and run attacker-controlled code with the victim’s account permissions. An employee must open the file, making phishing, shared files, and downloaded design assets plausible delivery paths. Successful exploitation could expose or alter data and disrupt the workstation.
Executive priority
Treat this as a high-priority workstation update, particularly for creative, publishing, and marketing teams. It is not evidenced as actively exploited, but successful compromise could affect confidentiality, integrity, and availability. Complete exposure inventory promptly and remediate affected installations through approved Adobe guidance.
Technical view
CVE-2026-27291 is a CWE-787 out-of-bounds write in Adobe InDesign Desktop. It affects versions 20.5.2, 21.2, and earlier. Opening a crafted file can cause arbitrary code execution as the current user. CVSS 3.1 scores it 7.8: local attack vector, low complexity, no privileges, and required user interaction.
Likely exposure
Exposure is concentrated on endpoints running affected InDesign versions, especially systems where users open externally supplied or untrusted design files. Accounts with elevated local privileges increase potential impact. The bundle does not identify affected operating systems or confirm whether previewing a file is sufficient.
Exploitation context
Exploitation requires a victim to open a malicious file; remote, interaction-free compromise is not supported by the supplied evidence. The CVE is not listed as KEV in the bundle, and no cited evidence confirms active exploitation or a public exploit.
Researcher notes
The supplied record establishes user-assisted arbitrary code execution through an out-of-bounds write. The affected-version metadata is awkwardly serialized, so the narrative description provides the clearest scope: 20.5.2, 21.2, and earlier. No root cause, file format, operating-system scope, exploit availability, or detection indicators are provided.
Mitigation direction
Update affected InDesign installations according to Adobe advisory APSB26-32.
Prioritize users who routinely receive design files from external parties.
Restrict or quarantine unsolicited InDesign files until endpoints are updated.
Avoid using administrative accounts for routine InDesign work.
Validation and detection
Inventory installed InDesign versions across managed and unmanaged endpoints.
Confirm no installations remain on 20.5.2, 21.2, or earlier.
Verify deployed versions against Adobe advisory APSB26-32.
Review endpoint controls for handling externally sourced InDesign files.
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-787: 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.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program 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-787 · source CWE mapping
Out-of-bounds Write
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.