dbcve.org
IncopyApplication · Adobe

CVE-2025-47098

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 an Access of Uninitialized Pointer 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 contains an access of uninitialized pointer vulnerability that can be exploited when a victim opens a maliciously crafted InCopy file. This memory corruption issue allows arbitrary code execution in the context of the current user's privileges.

MitigationUpdate InCopy to the latest patched version. Until a patch is available, instruct users to avoid opening InCopy files from untrusted sources and consider implementing application whitelisting or file reputation services.

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 InCopy version on Windows
    Open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\InCopy\Version (or HKLM\SOFTWARE\WOW6432Node\Adobe\InCopy\Version for 32-bit on 64-bit systems). Locate the Version or VersionNumber value to find the installed version.
    Affected if The installed version number is less than 19.5.4, or is 20.0 through 20.3.x.
  2. Check InCopy version on macOS
    Open Finder, navigate to /Applications/Adobe InCopy 2024 or Adobe InCopy 2025 folder. Right-click the InCopy application and select Get Info. Note the version number shown under General.
    Affected if The installed version number is less than 19.5.4, or is 20.0 through 20.3.x.
  3. Check InCopy version via Help menu
    Launch InCopy and go to Help > About InCopy (on Windows) or InCopy > About InCopy (on macOS). The version string displayed in the dialog window is the exact installed version.
    Affected if The version displayed is less than 19.5.4, or falls between 20.0 and 20.4 (excluding 20.4).
  4. Verify InCopy installation status
    Confirm that Adobe InCopy is installed and the application can be launched. Check for the presence of InCopy.exe (Windows) or InCopy app bundle (macOS) in typical installation paths such as C:\Program Files\Adobe\Adobe InCopy 2024 or /Applications/Adobe InCopy 2024/.
    Affected if The application is installed and executable, meaning users can open files with it.

A system is affected if Adobe InCopy is installed with a version less than 19.5.4, or between 20.0 and 20.4, allowing users to open potentially malicious InCopy 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 the latest patched version. Until a patch is available, instruct users to avoid opening InCopy files from untrusted sources and consider implementing application whitelisting or file reputation services.

Recommended fix High confidence

InCopy 19.5.4 (19.x branch) or InCopy 20.4 (20.x branch)

  1. Check current InCopy version by opening InCopy and going to Help > About InCopy
  2. If version is 19.x (e.g., 19.5.3 or earlier), download and install InCopy version 19.5.4 or later from Adobe's official download page
  3. If version is 20.x (e.g., 20.0 through 20.3), download and install InCopy version 20.4 or later from Adobe's official download page
  4. After installation, verify the version matches the fixed release (19.5.4+ or 20.4+)

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

Fix this in Incopy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,440
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,304.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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