CVE-2026-34700
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 write 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.
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 versions 21.3, 20.5.3 and earlier contain an out-of-bounds write vulnerability that can be triggered when a user opens a maliciously crafted file, leading to arbitrary code execution in the context of the current user's privileges.
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
- High
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
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, go to Help > About InDesign (or Help > System Info on Mac), or check via Creative Cloud desktop app under Installed appsAffected if Version shown is 21.3, 20.5.3 or earlier, or falls in the range >= 21.0 and < 21.4, or is < 20.5.4
-
Verify Windows installation path versionNavigate to C:\Program Files\Adobe\Adobe InDesign [version]\ and confirm folder name matches an affected version number, or check file properties of ID.exeAffected if Folder or executable version matches an affected version from step 1
-
Verify macOS installation path versionNavigate to /Applications/Adobe InDesign [version]/ and confirm folder name matches an affected version number, or check Get Info on Adobe InDesign appAffected if Folder or app version matches an affected version from step 1
User is affected if installed InDesign version is any version before 20.5.4 or any version from 21.0 up to and including 21.3.
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
Avoid opening untrusted or unexpected InDesign files from unknown sources. Apply the vendor patch when released and ensure endpoint protection tools monitor for suspicious file handling behaviors.
InDesign 20.5.4 or later for 20.x branch; InDesign 21.4 or later for 21.x branch
- Open Adobe Creative Cloud desktop application or navigate to Adobe InDesign download page
- Check current InDesign version by opening InDesign and going to Help > About InDesign
- If running version 20.x (e.g., 20.5.3 or earlier), upgrade to version 20.5.4 or later
- If running version 21.0-21.3, upgrade to version 21.4 or later
- Alternatively, use Adobe Creative Cloud app to update InDesign: open CC app, find InDesign in the Apps section, click Update
- After upgrade, verify the new version by checking Help > About InDesign
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation8.0 h
- Testing6.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 $5,600.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34700 — 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-34700 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