CVE-2025-47106
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 a Use After Free 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 a Use After Free vulnerability where memory is accessed after being freed, potentially exposing sensitive memory contents. An attacker can exploit this by crafting a malicious InDesign file that, when opened by a victim, allows memory disclosure and can bypass ASLR security mitigations.
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 installed InDesign versionOpen Adobe InDesign, then go to Help > About Adobe InDesign (or InDesign > About InDesign on Mac) to view the exact version number displayed in the dialogAffected if The version shown is below 19.5.4, or is 20.0, 20.1, or 20.2 (versions 20.0 through 20.2.x are affected)
-
Verify InDesign file opening capabilityConfirm that InDesign Desktop is configured to allow opening .indd and .idml files from the file system - this is the default behavior and required for the exploit to triggerAffected if Users can double-click or use File > Open to load InDesign documents, which is the standard workflow for this vulnerability
-
Confirm ASLR is not overriddenCheck that Address Space Layout Randomization (ASLR) is enabled on the system as a baseline security control - this can be verified via system security settings or tools like Process ExplorerAffected if ASLR is disabled system-wide, which would make exploitation easier though the vulnerability can still bypass ASLR when enabled
You are affected if Adobe InDesign Desktop version is either below 19.5.4, or falls between 20.0 and 20.3 (excluding 20.3), and users can open InDesign files from any source.
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
Apply vendor patches from Adobe when released. Until then, enforce policies prohibiting opening InDesign files from untrusted sources and maintain updated endpoint detection capabilities.
InDesign 19.5.4 or later for 19.x line; InDesign 20.3 or later for 20.x line
- 1. Identify the current installed version of Adobe InDesign by opening the application and checking Help > About InDesign
- 2. For InDesign versions 19.x (up to 19.5.3): Upgrade to version 19.5.4 or later
- 3. For InDesign versions 20.0-20.2: Upgrade to version 20.3 or later
- 4. Download the updated version from the official Adobe website or use Adobe Creative Cloud desktop application to update
- 5. After installation, verify the version by checking Help > About InDesign to confirm the update was successful
- 6. Exercise caution when opening files from untrusted sources, as exploitation requires user interaction to open a malicious file
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2025-47106 — 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-47106 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