CVE-2025-47136
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 19.5.3 and earlier are affected by an Integer Underflow (Wrap or Wraparound) 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 19.5.3 and earlier contain an integer underflow (wrap or wraparound) vulnerability. When parsing specially crafted malicious files, the integer underflow can be triggered leading to heap corruption and ultimately arbitrary code execution in the context of the current user. The attack requires user interaction—the victim must open a malicious .indd or related file.
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.4>= 20.0, < 20.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.
-
Check installed InDesign version on WindowsOpen Registry Editor and navigate to HKLM\SOFTWARE\Adobe\InDesign\[version] (e.g., 19.5 or 20.0) and read the 'InstallPath' value, or check C:\Program Files\Adobe\Adobe InDesign [version] folder. Alternatively, run 'Get-ItemProperty HKLM:\SOFTWARE\Adobe\InDesign\* -ErrorAction SilentlyContinue | Select-Object PSChildName' in PowerShell to list installed versions.Affected if The installed version is 19.5.3 or earlier, OR falls between 20.0 and 20.3.x inclusive.
-
Check installed InDesign version on macOSOpen Finder, navigate to /Applications/Adobe InDesign [version]/Adobe InDesign [version].app, right-click and select 'Get Info' to see the version number. Alternatively, run 'defaults read /Applications/Adobe\ InDesign\ */*.app/Contents/Info CFBundleShortVersionString' in Terminal to list versions.Affected if The installed version is 19.5.3 or earlier, OR falls between 20.0 and 20.3.x inclusive.
-
Confirm the specific version numberWithin the identified major version (19.x or 20.x), verify the exact minor/build number against the affected ranges. In InDesign, go to Help > About InDesign to see the full version string.Affected if Version is < 19.5.4 OR (version >= 20.0 AND version < 20.4).
-
Verify file association handlingCheck if .indd and related file types (.idml, .inx, .icml) are associated with InDesign by right-clicking any .indd file and selecting Properties > Opens with, or by examining registry key HKCR\.indd on Windows.Affected if The file types are associated with an unpatched InDesign installation (versions from step 1 or 3 indicate vulnerability).
A user is affected if their installed Adobe InDesign Desktop version is either 19.5.3 or earlier, or between 20.0 and 20.3.x inclusive, AND they open malicious .indd or related 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.420.4
Update InDesign Desktop to a version later than 19.5.3. Until patched, advise users not to open InDesign files from untrusted or unknown sources, and consider blocking InDesign file attachments at the email gateway.
19.5.4 for version 19.x users; 20.4 or later for version 20.x users
- 1. Verify current Adobe InDesign version by launching InDesign and navigating to Help > About InDesign
- 2. If running version 19.x (19.5.3 or earlier), upgrade to version 19.5.4 or later from Adobe's official download page
- 3. If running version 20.x (20.0-20.3), upgrade to version 20.4 or later from Adobe's official download page
- 4. Download the installer from helpx.adobe.com or your Adobe Creative Cloud desktop application
- 5. Close all running Adobe applications before installing
- 6. Run the installer and follow the prompts to complete the update
- 7. After installation, verify the version shows 19.5.4 or higher, or 20.4 or higher
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47136 — 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-47136 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