CVE-2026-34703
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 a NULL Pointer Dereference vulnerability that could result in an application denial-of-service. An attacker could exploit this vulnerability to crash the application, leading to a denial-of-service condition. 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 confidenceA NULL pointer dereference vulnerability in Adobe InDesign Desktop versions 21.3, 20.5.3 and earlier allows a maliciously crafted file to crash the application during parsing, causing a denial-of-service condition. The vulnerability is triggered when a victim opens a specially crafted file, causing the application to attempt to dereference a NULL pointer.
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
- None
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:N/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.
-
Confirm Adobe InDesign Desktop is installedOn Windows, check for the InDesign executable in Program Files or query the registry. On macOS, look for Adobe InDesign in the Applications folder.Affected if InDesign is not installed on the system, this CVE does not apply.
-
Locate the installed InDesign versionRun 'indesign -version' from command line, or right-click the InDesign executable, select Properties, and view the File Version or Product Version field.Affected if Unable to determine the version - treat as potentially vulnerable if InDesign is present.
-
Compare the installed version against affected rangesIdentify whether the version is in the 20.x or 21.x major line. For 20.x, check if version is less than 20.5.4. For 21.x, check if version is 21.0 through 21.3.Affected if Version 20.x below 20.5.4 OR version 21.0 through 21.3 indicates the installation is vulnerable to this CVE.
-
Assess user interaction exposureDetermine whether users in the environment open InDesign files from external or untrusted sources, as exploitation requires a victim to open a specially crafted malicious file.Affected if If users routinely open external InDesign files, the likelihood of triggerable exploitation increases.
System is affected only if Adobe InDesign Desktop is installed AND the version falls within 20.x < 20.5.4 or 21.0 <= version < 21.4.
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
Update InDesign to the patched version provided by Adobe. Until patched, exercise caution when opening files from untrusted sources.
InDesign 20.5.4 or later; InDesign 21.4 or later
- Open Adobe InDesign and navigate to Help > About InDesign to identify the current version number
- If the version is 20.x (20.5.3 or earlier), download and install InDesign version 20.5.4 or later from the official Adobe website
- If the version is 21.x (21.0 through 21.3), download and install InDesign version 21.4 or later from the official Adobe website
- After upgrading, verify the new version by checking Help > About InDesign
- Exercise caution when opening files from untrusted sources, as exploitation requires user interaction to open a malicious file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $3,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34703 — 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-34703 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