IndesignApplication · Adobe

CVE-2025-27166

HIGH · 7.8 CVSS v3.1 Published 2025-03-11
Fix available
A fix is available. Upgrade to 19.5.3 / 20.2 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 ID20.1, ID19.5.2 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 confidence

Adobe InDesign Desktop versions ID20.1, ID19.5.2 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution in the context of the current user when a victim opens a maliciously crafted InDesign file.

MitigationApply the vendor security update to InDesign to patched versions; avoid opening untrusted or unexpected InDesign files from unverified 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:< 19.5.3>= 20.0, < 20.2

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 installed InDesign version
    Open InDesign, then go to Help > About InDesign (or on Windows, check the version displayed in the application title bar or use the command 'reg query "HKLM\SOFTWARE\Adobe\InDesign" /v version' in Command Prompt)
    Affected if the displayed version number is less than 19.5.3 OR is 20.0 or 20.1 (versions 20.0 through 20.1 are all affected)
  2. Verify version via Windows registry
    Run 'reg query "HKLM\SOFTWARE\Adobe\InDesign" /s' or check 'HKLM\SOFTWARE\Adobe\InDesign\InstallPath' to locate the installation directory, then examine version.xml or the executable properties
    Affected if the version found is < 19.5.3 OR >= 20.0 but < 20.2
  3. Check macOS installation version
    Open Finder, navigate to Applications > Adobe InDesign, right-click and select Get Info, or run 'defaults read /Applications/Adobe\ InDesign\*/Adobe\ InDesign\*\ Info CFBundleShortVersionString' in Terminal
    Affected if the version string matches the affected ranges: any version below 19.5.3, or versions 20.0 through 20.1

You are affected if Adobe InDesign Desktop is installed with any version below 19.5.3 or between 20.0 and 20.1 inclusive.

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 19.5.3 / 20.2 or later
Fixed in 19.5.320.2
Interim mitigation

Apply the vendor security update to InDesign to patched versions; avoid opening untrusted or unexpected InDesign files from unverified sources.

Recommended fix High confidence

InDesign 19.5.3 (for 19.x line) or InDesign 20.2 (for 20.x line)

  1. Check current InDesign version: Open InDesign > Help > About InDesign
  2. Determine which major version line you are on (19.x or 20.x)
  3. For InDesign 19.x users: Download and install InDesign version 19.5.3 or later from helpx.adobe.com
  4. For InDesign 20.x users: Download and install InDesign version 20.2 or later from helpx.adobe.com
  5. Verify the update was successful by checking Help > About InDesign again

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

Fix this in Indesign Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-27166 — 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-2025-27166 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