dbcve.org
IncopyApplication · Adobe

CVE-2025-47099

HIGH · 7.8 CVSS v3.1 Published 2025-07-08
Fix available
A fix is available. Upgrade to 19.5.4 / 20.4 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.3, 19.5.3 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

InCopy versions 20.3, 19.5.3 and earlier contain a heap-based buffer overflow vulnerability when parsing malicious files. An attacker can craft a malicious .icml or related file that, when opened by a victim, triggers the overflow and enables arbitrary code execution in the context of the current user.

MitigationUpdate InCopy to version 20.3 or later (or the latest patched version). Avoid opening untrusted .icml or InCopy files from unknown sources until the update is 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.4>= 20.0, < 20.4

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. Check if Adobe InCopy is installed
    On Windows, check the registry key HKEY_LOCAL_MACHINE\SOFTWARE\Adobe\InCopy or HKEY_LOCAL_MACHINE\SOFTWARE\WOW6432Node\Adobe\InCopy for the InstallPath value, or look in C:\Program Files\Adobe\Adobe InCopy or C:\Program Files (x86)\Adobe\Adobe InCopy. On macOS, check /Applications/Adobe InCopy or the Application folder for Adobe InCopy.
    Affected if Adobe InCopy is found on the system
  2. Determine the installed InCopy version
    On Windows, read the Version value from the same registry key used above, or right-click the InCopy executable in Program Files and view Properties > Details. On macOS, right-click Adobe InCopy in Applications > Get Info to see the version number.
    Affected if The installed version is less than 19.5.4 OR is 20.0, 20.1, 20.2, or 20.3 (any version >= 20.0 but < 20.4)
  3. Identify the file type handler for .icml files
    On Windows, search the registry under HKEY_CLASSES_ROOT for .icml extension associations, or check the file type associations in the Windows Default Programs settings. Verify if InCopy is set as the default handler for .icml files.
    Affected if Adobe InCopy is associated as the default handler for .icml files
  4. Check for recent .icml file processing
    Review the user's recent documents or temp folders (such as %TEMP% or %USERPROFILE%\Documents) for .icml files that may have been opened. On Windows, check the Application event log for Adobe InCopy process events.
    Affected if Any .icml files from untrusted sources have been recently opened in InCopy

The environment is affected if Adobe InCopy is installed with a version below 19.5.4 or between 20.0 and 20.3 inclusive, and the user opens malicious .icml files.

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.4 / 20.4 or later
Fixed in 19.5.420.4
Interim mitigation

Update InCopy to version 20.3 or later (or the latest patched version). Avoid opening untrusted .icml or InCopy files from unknown sources until the update is applied.

Recommended fix High confidence

Adobe InCopy 19.5.4 or later, or 20.4 or later

  1. Close Adobe InCopy if it is currently running
  2. Open Adobe Creative Cloud desktop application on your system
  3. Navigate to the Updates section or find InCopy in the apps list
  4. Click Update to install the latest version, or manually check for updates
  5. Verify the installed version is 19.5.4 or later (for 19.x releases) or 20.4 or later (for 20.x releases)

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

Fix this in Incopy Scoped from the published advisory
  • Consultation2.0 h
  • Implementation3.0 h
  • Testing3.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,570
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,512.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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