CVE-2025-27175
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 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 · moderate confidenceInDesign Desktop versions 20.1, 19.5.2 and earlier contain an out-of-bounds write vulnerability. When a user opens a maliciously crafted file, the vulnerability triggers arbitrary code execution with the privileges of the current user.
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< 19.5.3>= 20.0, < 20.2CVSS 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.
-
Determine installed InDesign versionOpen InDesign, then go to Help > About Adobe InDesign (Windows) or InDesign > About InDesign (macOS). Alternatively, check the Windows Registry at HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InDesign\(version)\InstallPath or the macOS Application bundle at /Applications/Adobe InDesign */Info.plist for CFBundleShortVersionString.Affected if The displayed version number is lower than 19.5.3, OR is 20.0, 20.1, or any 20.x version lower than 20.2.
-
Confirm InDesign is presentSearch for InDesign application in the system: On Windows, look in C:\Program Files\Adobe\ or C:\Program Files (x86)\Adobe\. On macOS, check /Applications/ for Adobe InDesign.Affected if InDesign Desktop is installed on the system.
-
Identify trigger conditionThe vulnerability is triggered when a user opens a specially crafted malicious file. There is no configuration or feature flag that disables this; it is a parsing flaw in how InDesign handles certain file structures.Affected if A user with the vulnerable InDesign version opens a maliciously crafted .indd, .idml, or other InDesign file from an untrusted source.
The environment is affected if Adobe InDesign Desktop version is found to be below 19.5.3, or between 20.0 and 20.1.x inclusive, and the application is used to open files.
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 · scoped19.5.320.2
Update InDesign to the latest patched version and avoid opening files from untrusted or unverified sources.
InDesign 19.5.3 (for versions < 19.5.3) or InDesign 20.2 (for versions >= 20.0 and < 20.2)
- Verify current InDesign version by opening InDesign and navigating to Help > About InDesign
- Close InDesign completely before updating
- Open Adobe Creative Cloud desktop application
- Navigate to the Apps section
- Find Adobe InDesign in the installed apps list
- Click on Update next to InDesign to install the latest version
- Alternatively, download the update directly from helpx.adobe.com or the Adobe Creative Cloud downloads page
- Restart InDesign after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-27175 — 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-2025-27175 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