CVE-2025-47104
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.2, ID19.5.3 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. An attacker could leverage this vulnerability to bypass mitigations such as ASLR. 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 confidenceAdobe InDesign Desktop contains an out-of-bounds read vulnerability in affected versions (ID20.2, ID19.5.3 and earlier) that allows disclosure of sensitive memory contents when a user opens a malicious file. This memory disclosure can be leveraged to bypass ASLR mitigations, potentially facilitating further exploitation. The attack requires user interaction (opening a crafted file), reducing its exploitability compared to remote or silent attacks.
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.3CVSS 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
- None
- Availability
- None
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 InDesign installed version on WindowsOpen InDesign, go to Help > About Adobe InDesign, or check the file version of InDesign.exe in the installation folder (typically C:\Program Files\Adobe\Adobe InDesign 2024 or 2023\)Affected if The displayed version is 19.5.3 or earlier, OR between 20.0 and 20.2 inclusive (meaning versions < 19.5.4 or >= 20.0 but < 20.3)
-
Check InDesign installed version on macOSOpen InDesign, go to InDesign menu > About InDesign, or check the app bundle info via Get Info on the InDesign application in /ApplicationsAffected if The displayed version is 19.5.3 or earlier, OR between 20.0 and 20.2 inclusive (meaning versions < 19.5.4 or >= 20.0 but < 20.3)
-
Verify product is InDesign DesktopConfirm the installed product is Adobe InDesign Desktop (not InCopy, InServer, or other Creative Cloud applications)Affected if The vulnerable product is specifically Adobe InDesign Desktop as listed in the affected products
A user is affected if Adobe InDesign Desktop version is 19.5.3 or earlier, or 20.0 through 20.2, because these versions contain the out-of-bounds read that can expose memory contents when opening a malicious file.
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.3
Update InDesign Desktop to a patched version as specified in Adobe's security bulletin. Users should avoid opening files from untrusted sources to mitigate the user-interaction requirement for exploitation.
InDesign 19.5.4 or 20.3 and later
- 1. Close any running instances of Adobe InDesign
- 2. Open Adobe Creative Cloud desktop application or navigate to Adobe's official download page
- 3. Check for available updates to InDesign
- 4. If using InDesign version 19.x, update to version 19.5.4 or later
- 5. If using InDesign version 20.x, update to version 20.3 or later
- 6. Alternatively, download the specific fixed version directly from helpx.adobe.com
- 7. Install the update following the on-screen prompts
- 8. Restart InDesign after the update completes
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation2.0 h
- Testing4.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,464.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47104 — 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-47104 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