IncopyApplication · Adobe

CVE-2021-21090

HIGH · 8.8 CVSS v3.1 Published 2021-06-28
Fix available
A fix is available. Upgrade to after 16.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable 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
Adobe InCopy version 16.0 (and earlier) is affected by an path traversal vulnerability when parsing a crafted file. An unauthenticated attacker could leverage this vulnerability to achieve remote 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 16.0 and earlier contain a path traversal vulnerability when parsing crafted files. By embedding path traversal sequences (e.g., ../) in a malicious file, an attacker can write arbitrary files to the filesystem and achieve remote code execution in the context of the user who opens the file.

MitigationUpdate Adobe InCopy to version 16.1 or later. Until patched, avoid opening InCopy files from untrusted 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:<= 16.0

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
Network
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/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. Confirm Adobe InCopy is installed
    Check for InCopy installation: On Windows, look in Program Files/Adobe or use 'Get-ItemProperty' registry query for HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\* | Where-Object {$_.DisplayName -like '*InCopy*'}. On macOS, check /Applications for Adobe InCopy.
    Affected if Adobe InCopy is found on the system
  2. Identify the installed version number
    Run the application and check About, or query the version via registry on Windows: Get-ItemProperty 'HKLM:\SOFTWARE\Adobe\InCopy' -Name CurrentVersion, or check the executable properties at Program Files/Adobe/InCopyVersionFolder/InCopy.exe
    Affected if Version returned is 16.0 or earlier
  3. Compare version to affected range
    Match the discovered version against the affected range: versions 16.0 and earlier are vulnerable, version 16.1 and later are patched
    Affected if Installed version is 16.0 or earlier
  4. Determine exposure to untrusted files
    Assess whether users open InCopy files (.icml, .icap, .inx) from untrusted or unknown sources, as exploitation requires opening a crafted malicious file
    Affected if Users routinely open InCopy files from untrusted sources without verification

A system is affected if Adobe InCopy version 16.0 or earlier is installed AND users may open InCopy files from untrusted sources, as the vulnerability triggers during file parsing.

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 a release after 16.0
Interim mitigation

Update Adobe InCopy to version 16.1 or later. Until patched, avoid opening InCopy files from untrusted sources.

Recommended fix Moderate confidence

Adobe InCopy 16.1 or later

  1. 1. Open Adobe InCopy
  2. 2. Navigate to Help > Check for Updates
  3. 3. Download and install the available security update
  4. 4. Alternatively, download the latest version of Adobe InCopy from the official Adobe website
  5. 5. Verify the installed version is 16.1 or later by going to Help > About Adobe InCopy
Caveat Minor: Some legacy file format compatibility settings may have changed; back up custom workspaces and preferences before updating

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

Fix this in Incopy Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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