InDesign Desktop versions 21.1, 20.5.1 and earlier are affected by a Heap-based Buffer Overflow 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 file can exploit a memory-handling flaw when opened, potentially letting an attacker run code with the victim’s account permissions. This could expose files, alter data, or disrupt the workstation. The user must open the file, which limits—but does not remove—the risk.
Executive priority
Treat this as a high-priority workstation update, especially for creative, publishing, and marketing teams handling external files. It is not described as a remote, interaction-free compromise, but successful exploitation could provide the attacker the victim’s access and materially affect sensitive data and operations.
Technical view
CVE-2026-21357 is a heap-based buffer overflow (CWE-122) in Adobe InDesign Desktop. A crafted file may trigger arbitrary 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 impact.
Likely exposure
Exposure is most likely on endpoints running InDesign 21.1, 20.5.1, or earlier, particularly where users receive or download untrusted design files. Impact depends on the permissions of the user opening the file. Systems running the newer version boundaries identified in the bundle are not described as affected.
Exploitation context
Successful exploitation requires a victim to open a malicious file. The supplied sources do not establish active exploitation, and the CVE is not identified as being in CISA KEV. Absence from KEV is not proof that exploitation has never occurred.
Researcher notes
The supplied affected-version structure is ambiguous, but the narrative explicitly identifies 21.1, 20.5.1, and earlier as affected and points to 21.2 and 20.5.2 as newer boundaries. No root cause beyond CWE-122, proof of concept, attack campaign, or active exploitation evidence is provided. Validate release-specific applicability against Adobe’s advisory.
Mitigation direction
Update InDesign to 21.2, 20.5.2, or a later vendor-supported release, as applicable.
Prioritize endpoints whose users regularly open externally supplied InDesign files.
Restrict or quarantine unexpected InDesign files from email, downloads, and collaboration channels.
Apply least privilege so successful code execution has limited account access.
Review Adobe’s advisory for any revised remediation or platform-specific guidance.
Validation and detection
Inventory installed InDesign versions across managed endpoints.
Confirm versions 21.1, 20.5.1, and earlier have been upgraded or isolated.
Verify software-management reports show the intended update installed successfully.
Review endpoint telemetry for suspicious activity following InDesign file opens.
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-122: 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-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.