IndesignApplication · Adobe

CVE-2025-54228

MEDIUM · 5.5 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 19.5.5 / 20.5 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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 · unedited
InDesign Desktop versions 20.4, 19.5.4 and earlier are affected by an out-of-bounds read vulnerability that could lead to disclosure of sensitive memory. 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 confidence

Adobe InDesign Desktop versions 20.4, 19.5.4 and earlier contain an out-of-bounds read vulnerability that allows disclosure of sensitive memory contents when a user opens a specially crafted malicious file.

MitigationUpdate InDesign to the latest patched version available from Adobe. Until patched, avoid opening untrusted .indd files from unknown sources.

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
IndesignApplication
Affected:< 19.5.5>= 20.0, < 20.5

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check installed InDesign version on Windows
    Open Control Panel > Programs and Features, locate Adobe InDesign in the list, and note the version number shown in the Version column
    Affected if The version listed is earlier than 19.5.5, or is 20.0 through 20.4.x
  2. Check installed InDesign version on macOS
    Open Finder > Applications > Adobe InDesign, click on the application, then use File > Get Info (or press Cmd+I) to view the version number
    Affected if The version shown is earlier than 19.5.5, or is 20.0 through 20.4.x
  3. Check InDesign version from within the application
    Launch InDesign, then go to Help > About Adobe InDesign. The version number displayed in the About window is your installed version
    Affected if The About window shows a version earlier than 19.5.5, or shows 20.0 through 20.4.x
  4. Verify the specific vulnerable version range
    Compare your identified version against the affected ranges: versions 19.x below 19.5.5, and versions 20.0 through 20.4.x are vulnerable. Versions 19.5.5 and later, and 20.5 and later are not affected
    Affected if Your version falls within 19.0 to 19.5.4, or within 20.0 to 20.4.x

You are affected if InDesign Desktop is installed with a version lower than 19.5.5, or with a version in the 20.0 to 20.4.x range.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 19.5.5 / 20.5 or later
Fixed in 19.5.520.5
Interim mitigation

Update InDesign to the latest patched version available from Adobe. Until patched, avoid opening untrusted .indd files from unknown sources.

Recommended fix High confidence

Adobe InDesign 20.5 or later (or 19.5.5 or later for the legacy 19.x branch)

  1. 1. Close Adobe InDesign if currently running
  2. 2. Navigate to the official Adobe website and download Adobe InDesign version 20.5 or later (or version 19.5.5 or later for the 19.x branch)
  3. 3. Run the Adobe InDesign installer and follow the on-screen prompts to complete the installation
  4. 4. After installation completes, restart your computer to ensure all components are properly updated
  5. 5. Launch Adobe InDesign and verify the version number matches the updated release (20.5.x or 19.5.5)
Caveat Review Adobe's compatibility documentation for known issues with third-party plugins or scripts when upgrading major versions

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Indesign Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing4.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,340
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,144.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54228 — 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 sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2025-54228 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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