CVE-2026-34705
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.3, 20.5.3 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to disclose sensitive information. 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 · high confidenceAdobe InDesign Desktop contains an out-of-bounds read vulnerability in versions 21.3, 20.5.3 and earlier. The vulnerability allows reading beyond allocated memory boundaries, potentially exposing sensitive memory contents. Successful exploitation requires a victim to open a specially crafted malicious InDesign file.
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.4>= 21.0, < 21.4CVSS 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 InDesign, go to Help > About InDesign (or press Ctrl+Alt+Shift+N on Windows, Cmd+Option+Shift+N on macOS). Note the full version number displayed.Affected if The displayed version falls within < 20.5.4 or >= 21.0 and < 21.4
-
Check InDesign version via application fileNavigate to the InDesign installation directory (typically C:\Program Files\Adobe\Adobe InDesign 202X on Windows or /Applications/Adobe InDesign 202X on macOS). Right-click the InDesign executable, select Properties, and view the File Version details.Affected if The file version matches an affected release: 20.x versions before 20.5.4, or 21.0 through 21.3.x
-
Verify version via Windows Registry (Windows only)Open Registry Editor, navigate to HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InDesign\InstalledVersion (or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\InDesign\InstalledVersion for 32-bit on 64-bit Windows). Read the default value string.Affected if The version string indicates a release before 20.5.4 in the 20.x line, or between 21.0 and 21.3.x in the 21.x line
-
Confirm application is actively usedCheck if InDesign is actively used in the environment by reviewing installed software lists, license records, or user access logs showing recent application launches.Affected if InDesign is installed and users have access to open files with it, which combined with an affected version means exposure to the flaw
You are affected if InDesign is installed with a version lower than 20.5.4 in the 20.x line, or between 21.0 and 21.3.x in the 21.x line, and users can open files in 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.421.4
Users should refrain from opening InDesign files from untrusted or unknown sources. Apply Adobe's official security patches when released. Consider implementing enterprise file type restrictions and user security awareness training.
InDesign 20.5.4 or later; InDesign 21.4 or later
- 1. Close all Adobe InDesign instances
- 2. For InDesign version 20.x users: Upgrade to InDesign version 20.5.4 or later
- 3. For InDesign version 21.x users: Upgrade to InDesign version 21.4 or later
- 4. Download the updated version from the official Adobe website or use Adobe Creative Cloud desktop application to update
- 5. After installation, verify the version by going to Help > About InDesign
- 6. Do not open untrusted or unsolicited InDesign files to mitigate the user interaction requirement for exploitation
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34705 — 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-34705 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