Raw vector
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HSummary
CVE-2026-21275 is a high-severity Access of Uninitialized Pointer (CWE-824) vulnerability in Adobe Indesign. Its CVSS base score is 7.8 (High).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploitation for Privilege Escalation (T1068); ranked at the 13th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog.
The strongest mitigations our analysis identified map to SA-11 (Developer Testing and Evaluation) and SA-15 (Development Process, Standards, and Tools) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-21275 is an Access of Uninitialized Pointer vulnerability (CWE-824) affecting Adobe InDesign Desktop versions 21.0, 19.5.5, and earlier. The flaw allows arbitrary code execution in the context of the current user when processing malicious files. It has a CVSS v3.1 base score of 7.8 (AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H), indicating high impact with local access required, low attack complexity, no privileges needed, and user interaction.
Exploitation requires a victim to open a specially crafted malicious file in a vulnerable InDesign instance, enabling an attacker with local access to the system to achieve arbitrary code execution as the current user. This could lead to full compromise of the user's session, including high confidentiality, integrity, and availability impacts, though it does not escalate privileges or change scope.
Adobe's security bulletin (APSB26-02) at https://helpx.adobe.com/security/products/indesign/apsb26-02.html provides details on the vulnerability and available patches for mitigation. Security practitioners should ensure affected InDesign versions are updated promptly to address this issue.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-2054
Vulnerability Data
InDesign Desktop versions 21.0, 19.5.5 and earlier are affected by an Access of Uninitialized Pointer 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…
more
victim must open a malicious file.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Developer testing and evaluation can discover uninitialized pointer accesses through static analysis, dynamic testing, or fuzzing before deployment.
Requiring documented development processes and tools enables use of analyzers or coding standards that identify uninitialized pointer defects.
Security engineering principles can mandate memory-safety practices and language choices that structurally avoid uninitialized pointer use.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly prevent uninitialized pointer bugs via coding standards, analysis, and reviews, but eliminating this single weakness only partially fulfills the broader control.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing can detect uninitialized pointer usage before release.
Secure development life cycle mandates practices that reduce uninitialized pointer defects.
Application security requirements can specify pointer initialization rules.
Secure architecture principles discourage unsafe pointer handling.
Secure coding standards directly prohibit use of uninitialized pointers.