InDesign Desktop versions 21.0, 19.5.5 and earlier are affected by an Out-of-bounds Read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to access sensitive information stored in memory. 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 could cause affected desktop versions to reveal sensitive information from application memory when opened. The victim must interact by opening the file. The supplied evidence describes confidentiality loss, not file modification or service disruption.
Executive priority
Treat this as a normal-priority desktop remediation with higher urgency for creative teams handling external files or sensitive data. It is not supported as an emergency exploitation event, but affected endpoints should be updated promptly because successful exploitation may expose confidential memory contents.
Technical view
CVE-2026-21278 is a CWE-125 out-of-bounds read in Adobe InDesign Desktop. It has CVSS 3.1 score 5.5: local attack vector, low complexity, no privileges, required user interaction, high confidentiality impact, and no stated integrity or availability impact.
Likely exposure
Risk is concentrated on endpoints running InDesign Desktop 21.0, 19.5.5, or earlier, particularly where users open externally supplied design files. The structured affected-version data is ambiguous, so confirm exact applicability against Adobe's advisory.
Exploitation context
Exploitation requires convincing a user to open a malicious file. The supplied bundle does not report active exploitation, and the CVE is not identified as being in KEV. No exploit method or observed campaign is documented here.
Researcher notes
The description identifies versions 21.0, 19.5.5, and earlier, while the structured affected field contains ambiguous values including 21.1 and 20.5.1 with a default-unaffected status. Use Adobe's advisory as the authority for precise version boundaries. The supplied evidence establishes an out-of-bounds read but provides no root-cause detail, indicators, or exploit telemetry.
Mitigation direction
Follow Adobe's advisory and install the applicable security update or supported release.
Prioritize systems whose users regularly receive InDesign files from external parties.
Restrict or quarantine untrusted InDesign documents until affected systems are updated.
Reinforce user caution around unsolicited or unexpected design files.
Validation and detection
Inventory installed InDesign Desktop versions across managed endpoints.
Compare each installed version with the exact ranges in Adobe's advisory.
Verify the applicable security update is installed and remains after restart.
Review controls for scanning or quarantining externally received 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-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.
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.