dbcve.org
IncopyApplication · Adobe

CVE-2025-54218

HIGH · 7.8 CVSS v3.1 Published 2025-08-12
Fix available
A fix is available. Upgrade to 19.5.5 / 20.5 or later.
See remediation →
81/100
Remediation priority · High
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
InCopy versions 20.4, 19.5.4 and earlier are affected by an out-of-bounds write 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 confidence

Adobe InCopy versions 20.4, 19.5.4 and earlier contain an out-of-bounds write vulnerability that allows arbitrary code execution when a user opens a maliciously crafted InCopy document. The vulnerability exploits the lack of proper bounds checking during file parsing, enabling an attacker to overwrite memory and execute arbitrary code in the context of the current user.

MitigationApply the vendor-supplied security patch to upgrade InCopy to a fixed version, and instruct users to avoid opening InCopy documents from untrusted or 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
IncopyApplication
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
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 checks

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

  1. Verify Adobe InCopy is installed
    Search for InCopy on the system: on Windows, look for the incopy.exe process or check Program Files for Adobe InCopy folder; on macOS, check /Applications for Adobe InCopy.app
    Affected if Adobe InCopy is present on the system
  2. Determine the installed InCopy version number
    On Windows, right-click incopy.exe, select Properties, and view the Product Version in the Details tab; on macOS, right-click Adobe InCopy.app, select Get Info, and view the Version number; alternatively, open InCopy and go to Help > About Adobe InCopy
    Affected if Unable to determine the version or version is found
  3. Compare the installed version against the affected ranges
    Check if the version is less than 19.5.5 (any 19.x.x version below 19.5.5) OR if the version is 20.0 through 20.4.x (any 20.x.x version below 20.5)
    Affected if The version is less than 19.5.5 OR is 20.0 to 20.4.x inclusive

The environment is affected if Adobe InCopy is installed and the installed version is below 19.5.5 or falls between 20.0 and 20.4.x.

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

Apply the vendor-supplied security patch to upgrade InCopy to a fixed version, and instruct users to avoid opening InCopy documents from untrusted or unknown sources.

Recommended fix High confidence

Adobe InCopy 19.5.5 (for 19.x branch) or 20.5 (for 20.x branch)

  1. Close Adobe InCopy if currently running
  2. Identify your current InCopy version via Help > About Adobe InCopy
  3. If running version 19.x (< 19.5.5), download Adobe InCopy 19.5.5 from the official Adobe website
  4. If running version 20.0 - 20.4, download Adobe InCopy 20.5 from the official Adobe website
  5. Run the installer and complete the upgrade following the on-screen prompts
  6. After installation, verify the fix by checking Help > About Adobe InCopy to confirm version 19.5.5 or 20.5
  7. Exercise caution when opening files from untrusted sources, even after patching

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

Fix this in Incopy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation2.0 h
  • Testing1.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,090
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2025-54218 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

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-54218 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