CVE-2026-21332
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedInDesign Desktop versions 21.1, 20.5.1 and earlier are affected by an out-of-bounds read vulnerability that could lead to memory exposure. An attacker could leverage this vulnerability to disclose sensitive information stored in memory. Exploitation of this issue requires user interaction in that a victim must open a malicious file.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceAdobe InDesign Desktop versions 21.1, 20.5.1 and earlier contain an out-of-bounds read vulnerability during file parsing. When a victim opens a maliciously crafted InDesign file, the application reads memory beyond allocated boundaries, potentially exposing sensitive data stored in process memory.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data< 20.5.2>= 21.0, < 21.2CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Local
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed InDesign versionOpen Adobe InDesign and navigate to Help > About InDesign (Windows) or InDesign > About InDesign (Mac), or check the installed version in Windows Control Panel > Programs and Features, or macOS Applications folderAffected if version is 20.5.1 or earlier, or version is 21.0 or 21.1 (these fall within < 20.5.2 or >= 21.0 and < 21.2)
-
Confirm version falls within affected rangeCompare your installed version number to the vulnerable ranges: versions before 20.5.2, and versions 21.0 through 21.1Affected if installed version is 20.5.1 or earlier, OR installed version is exactly 21.0 or 21.1
-
Determine if file parsing is accessibleThis vulnerability is triggered when InDesign parses specially crafted .indd or .idml files. Verify if users have the ability to open files from external sourcesAffected if users can open InDesign files from untrusted or unsolicited sources
You are affected if InDesign version is 20.5.1 or earlier, or version 21.0 or 21.1, and users in your environment open InDesign files (which is the normal function of the application).
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped20.5.221.2
Users should refrain from opening untrusted or unsolicited InDesign files. Organizations should deploy the vendor patch once available, prioritizing workstations with access to sensitive data.
InDesign 20.5.2 or later for version 20.x; InDesign 21.2 or later for version 21.x
- 1. Check your current InDesign version by going to Help > About InDesign
- 2. If running version 20.5.1 or earlier, upgrade to version 20.5.2 or later
- 3. If running version 21.0 or 21.1, upgrade to version 21.2 or later
- 4. Open Adobe Creative Cloud desktop application and navigate to the Apps tab
- 5. Find Adobe InDesign in the installed apps list and click Update to install the latest version
- 6. Alternatively, download the updated installer from helpx.adobe.com
- 7. After installation, verify the version by checking Help > About InDesign to confirm the patch was applied
- 8. Test with existing documents to ensure compatibility
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation3.0 h
- Implementation8.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-21332 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-21332 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data