dbcve.org
IncopyApplication · Adobe

CVE-2025-54219

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 a Heap-based Buffer Overflow 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

Heap-based buffer overflow vulnerability in Adobe InCopy versions 20.4, 19.5.4 and earlier allows arbitrary code execution when a victim opens a maliciously crafted file, executing in the context of the current user.

MitigationUpdate InCopy to version 20.5, 19.5.5, or later per Adobe's official security advisory. Avoid opening files from untrusted sources until patches are applied.

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
    On Windows, open Programs and Features or search for InCopy in the Start menu. On macOS, open Finder and navigate to /Applications to confirm Adobe InCopy is present.
    Affected if InCopy is present on the system
  2. Find the installed InCopy version on Windows
    Right-click the InCopy executable (usually in C:\Program Files\Adobe\Adobe InCopy 202X or similar) and select Properties, then inspect the Details tab for the Product Version field. Alternatively, open InCopy and go to Help > About InCopy.
    Affected if The displayed version is 20.4, 19.5.4, or any version < 19.5.5 or >= 20.0 but < 20.5
  3. Find the installed InCopy version on macOS
    Right-click Adobe InCopy in /Applications, select Get Info, and check the Version field under General. Alternatively, open InCopy and go to InCopy menu > About InCopy.
    Affected if The displayed version is 20.4, 19.5.4, or any version < 19.5.5 or >= 20.0 but < 20.5
  4. Compare your version against vulnerable ranges
    If you have version 20.x, ensure it is 20.5 or later. If you have version 19.x, ensure it is 19.5.5 or later. Any version below these thresholds is within the affected range.
    Affected if Installed version is earlier than 19.5.5, or is 20.0 through 20.4

You are affected if Adobe InCopy is installed and the version number is less than 19.5.5, or is 20.0 through 20.4.

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 InCopy to version 20.5, 19.5.5, or later per Adobe's official security advisory. Avoid opening files from untrusted sources until patches are applied.

Recommended fix High confidence

Adobe InCopy 19.5.5 or 20.5 (depending on your release line)

  1. 1. Close Adobe InCopy if it is currently running
  2. 2. Open a web browser and navigate to the Adobe InCopy download page at helpx.adobe.com
  3. 3. Locate the download link for InCopy version 19.5.5 (for users on version 19.x) or version 20.5 (for users on version 20.x)
  4. 4. Download the appropriate installer for your operating system
  5. 5. Run the downloaded installer and follow the on-screen prompts to complete the installation
  6. 6. Restart your computer if prompted
  7. 7. After installation, verify the installed version by opening InCopy and checking the version number in Help > About Adobe InCopy
Caveat Adobe software updates typically preserve user settings and preferences; however, test critical workflows after upgrading

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
  • Testing2.0 h
  • Review / QA1.0 h
7.0 hours of engineering $1,240
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,984.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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