InDesign Desktop 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
A malicious InDesign file can trigger a memory-handling flaw when opened, potentially allowing attacker-controlled code to run with the victim’s account permissions. The risk is highest for employees who receive design files from customers, contractors, or other external sources. Opening the file is required; this is not described as a remotely exploitable, no-click issue.
Executive priority
Treat this as a high-priority user-endpoint update, especially where external design files are routine. It is not described as no-click or remotely reachable, but successful exploitation could compromise business data and endpoint integrity. Accelerate remediation for privileged users and externally facing creative workflows.
Technical view
CVE-2026-27284 is a CWE-125 out-of-bounds read in Adobe InDesign Desktop’s crafted-file parser. A read beyond an allocated memory structure may lead to code execution as the current user. The CVSS 3.1 score is 7.8: local attack vector, low complexity, no privileges required, user interaction required, unchanged scope, and high confidentiality, integrity, and availability impacts.
Likely exposure
Exposure exists where InDesign Desktop 20.5.2, 21.2, or earlier supported branches remain installed and users open untrusted files. Creative, publishing, and document-production teams exchanging files externally are likely priorities. The supplied evidence does not identify other Adobe products, server-side exposure, or specific operating systems.
Exploitation context
Exploitation requires convincing a user to open a crafted file. Successful exploitation could execute code with that user’s privileges. The source bundle marks the CVE as absent from KEV and provides no cited evidence of active exploitation; this does not prove exploitation has never occurred.
Researcher notes
The supplied version data appears to indicate affected cutoffs of 20.5.2 and 21.2, with 20.5.3 and 21.3 as later boundaries. Confirm exact fixed builds and platform applicability in APSB26-32 before compliance decisions. No technical root-cause detail, proof of concept, indicators, or confirmed exploitation evidence is included.
Mitigation direction
Update affected installations beyond 20.5.2 or 21.2, following Adobe advisory APSB26-32 and supported release guidance.
Prioritize systems whose users routinely receive or open InDesign files from external parties.
Until updated, restrict opening unsolicited or untrusted InDesign files and use established file-screening controls.
Apply least privilege to InDesign users to reduce the consequences of code execution.
Validation and detection
Inventory installed InDesign Desktop versions and identify installations at 20.5.2, 21.2, or earlier.
Confirm updated branches report versions newer than the affected cutoffs and match Adobe’s advisory.
Verify endpoint-management reports show successful rollout across creative and publishing systems.
Review security telemetry for suspicious activity following recently opened InDesign files; available sources provide no specific indicators.
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.