IndesignApplication · Adobe

CVE-2026-34628

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 20.5.3 / 21.3 or later.
See remediation →
81/100
Remediation priority · High
No privileges

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 · unedited
InDesign Desktop versions 20.5.2, 21.2 and earlier are affected by a Heap-based Buffer Overflow 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 confidence

Adobe InDesign Desktop versions 20.5.2, 21.2 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a specially crafted malicious file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate InDesign to a patched version beyond 21.2 and avoid opening untrusted or unexpected InDesign files from unknown sources.

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
IndesignApplication
Affected:< 20.5.3>= 21.0, < 21.3

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify InDesign installation path
    On Windows, check C:\Program Files\Adobe\ for Adobe InDesign folders. On Mac, check /Applications/ for Adobe InDesign.app. Note the installed version folder names (e.g., 'Adobe InDesign 2024' or 'Adobe InDesign 2025').
    Affected if If Adobe InDesign is present in standard application directories
  2. Determine installed InDesign version number
    On Windows: Right-click InDesign.exe in the installation folder, select Properties, view the Details tab for Product Version. On Mac: Right-click Adobe InDesign.app, select Get Info, read the Version field.
    Affected if Version displays as 20.5.2 or earlier in the 20.x series, OR displays as 21.0, 21.1, or 21.2 in the 21.x series
  3. Check all InDesign installations
    If multiple versions are installed (common with Adobe CC), check each InDesign.exe or InDesign.app individually using the method above.
    Affected if Any installed instance is version 20.5.2 or earlier, or between 21.0 and 21.2 inclusive

You are affected if any installed Adobe InDesign version is below 20.5.3 (for 20.x releases) or falls within 21.0 through 21.2 (for 21.x releases).

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 20.5.3 / 21.3 or later
Fixed in 20.5.321.3
Interim mitigation

Update InDesign to a patched version beyond 21.2 and avoid opening untrusted or unexpected InDesign files from unknown sources.

Recommended fix High confidence

InDesign 20.5.3 or later, or InDesign 21.3 or later

  1. 1. Close any running instances of Adobe InDesign
  2. 2. Open Adobe Creative Cloud desktop application or navigate to adobe.com
  3. 3. Go to the InDesign product page or open the Creative Cloud apps panel
  4. 4. Check for available updates - the update should include the security fix
  5. 5. If automatic updates are enabled, InDesign will prompt you to update; otherwise, click the Update button
  6. 6. Wait for the update to download and install completely
  7. 7. Verify the installed version by opening InDesign and going to Help > About InDesign
  8. 8. Confirm the version number is 20.5.3 or later, OR 21.3 or later
Caveat Adobe security updates typically include only bug fixes and security patches with minimal risk of breaking changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Indesign Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34628 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34628 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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