CVE-2025-47105
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 · high confidenceAdobe InDesign Desktop versions ID20.2, ID19.5.3 and earlier contain an out-of-bounds read vulnerability that allows reading memory beyond allocated buffers. This can expose sensitive memory contents and be leveraged to defeat ASLR (Address Space Layout Randomization), a critical memory protection mechanism. Exploitation requires a victim to open a specially crafted malicious 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.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.
-
Identify installed InDesign version on WindowsOpen Registry Editor and navigate to HKLM\SOFTWARE\Adobe\InDesign\InstallVersion, or open InDesign and go to Help > About InDesign to view the exact version numberAffected if The displayed version is earlier than 19.5.4, or falls between 20.0 and 20.2.x (including 20.0, 20.1, 20.2)
-
Identify installed InDesign version on macOSOpen Finder, go to /Applications, right-click Adobe InDesign, select Get Info to view the version, or use System Information > Applications to list installed Adobe softwareAffected if The displayed version is earlier than 19.5.4, or falls between 20.0 and 20.2.x (including 20.0, 20.1, 20.2)
-
Confirm the attack vector requires user interactionUnderstand that exploitation requires a victim to open a specially crafted malicious InDesign file (IDML or similar)Affected if Users in the environment open InDesign files from untrusted sources (email attachments, downloads from unknown sources)
You are affected if InDesign Desktop is installed at a version earlier than 19.5.4, or at version 20.0 through 20.2.x, and users may open untrusted InDesign 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.3
Update InDesign to the latest patched version provided by Adobe. Additionally, implement controls to prevent opening untrusted files, such as email attachment filtering, user awareness training, and endpoint detection tools.
InDesign 19.5.4 or InDesign 20.3
- Download InDesign version 19.5.4 (for InDesign 19.x users) or version 20.3 (for InDesign 20.x users) from the official Adobe website
- Install the updated InDesign version over the existing installation
- Restart InDesign after installation
- Verify the installed version matches the fixed release (19.5.4 or 20.3)
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-47105 — 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-47105 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