CVE-2025-43589
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 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 ID20.2, ID19.5.3 and earlier contain a Use After Free (UAF) memory corruption vulnerability. When a user opens a specially crafted malicious file, the vulnerability allows an attacker to freed memory to be accessed, potentially leading to arbitrary code execution at the current user's privilege level.
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
- 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.
-
Locate InDesign installation directoryOn Windows, check C:\Program Files\Adobe\Adobe InDesign [Version] or C:\Program Files (x86)\Adobe\Adobe InDesign [Version]. On Mac, check /Applications/Adobe InDesign [Version]. The version folder name typically contains the version number (e.g., ID20.0, ID19.5).Affected if InDesign is installed in a standard location and the folder name contains the version number.
-
Identify installed InDesign version numberRight-click the InDesign.exe (Windows) or Get Info on Adobe InDesign.app (Mac), then view the Details tab or Version field to see the exact build number (e.g., 20.2.0.77 or 19.5.3.60).Affected if The version displayed is ID20.2, ID19.5.3, or any version number lower than these.
-
Compare version against affected rangesCheck if your installed version falls into these affected ranges: any version before 19.5.4 (such as 19.5.3, 19.5.2, 19.4, etc.) OR any version from 20.0 up to but not including 20.3 (such as 20.0, 20.1, 20.2). Versions 19.5.4 and above, or 20.3 and above, are not affected.Affected if Your installed version is < 19.5.4 OR is >= 20.0 but < 20.3.
-
Assess file opening behaviorThe vulnerability triggers when InDesign opens a specially crafted malicious .indd, .idml, or other InDesign file. Determine if users in your environment open InDesign files from untrusted or unknown sources, as this is required for exploitation.Affected if Users routinely open InDesign files from email attachments, downloads, or external sources without verification.
You are affected if your installed InDesign version is below 19.5.4 or between 20.0 and 20.2, 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 released by Adobe to address this vulnerability. Avoid opening untrusted InDesign files from unknown sources until the patch is applied.
InDesign 19.5.4 or later for 19.x releases; InDesign 20.3 or later for 20.x releases
- 1. Close Adobe InDesign if it is currently running
- 2. Open Adobe Creative Cloud desktop application or navigate to the Adobe InDesign download page
- 3. Check your current InDesign version by opening InDesign and going to Help > About InDesign
- 4. If running version 19.x (< 19.5.4): Update to version 19.5.4 or later
- 5. If running version 20.x (>= 20.0 and < 20.3): Update to version 20.3 or later
- 6. Alternatively, download the specific installer from helpx.adobe.com by searching for the InDesign security update
- 7. Run the installer and follow the prompts to complete the upgrade
- 8. After installation, verify the version by checking Help > About InDesign to confirm the patch was applied
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-43589 — 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-43589 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