dbcve.org
IncopyApplication · Adobe

CVE-2026-21281

HIGH · 7.8 CVSS v3.1 Published 2026-01-13
Fix available
A fix is available. Upgrade to 20.5.1 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 21.0, 19.5.5 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

Adobe InCopy versions 21.0, 19.5.5 and earlier contain a heap-based buffer overflow vulnerability that can be triggered by opening a malicious file. Successful exploitation allows arbitrary code execution with the privileges of the user who opened the file. The CVSS 7.8 score indicates high severity due to the potential for complete compromise of user-level access.

MitigationUpdate InCopy to the latest version available from Adobe. Avoid opening files from untrusted or unknown sources until the patch is applied, as exploitation requires user interaction.

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:< 20.5.1= 21.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
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. Determine installed Adobe InCopy version
    On Windows, right-click the InCopy executable (typically in Program Files/Adobe), select Properties, and view the Version tab. On macOS, right-click the InCopy application, select Get Info, and check the Version field. Alternatively, open InCopy and go to Help > About InCopy to display the exact version number.
    Affected if The displayed version is 21.0 or any version earlier than 20.5.1 (such as 19.5.5 or earlier).
  2. Verify the exact version string
    Record the full version number displayed (for example, 21.0.0.x or 19.5.5.x). Adobe versions may include a fourth numeric segment that must be noted precisely.
    Affected if The version begins with 21.0 (any 21.0.x.x release) or begins with any version lower than 20.5.1.
  3. Confirm InCopy is present on the system
    Search for InCopy executable files: on Windows, look for 'INCOPY.EXE' in Adobe program folders; on macOS, look for 'Adobe InCopy' in the Applications folder.
    Affected if InCopy is installed and the version cannot be determined or falls within the affected ranges.

You are affected if Adobe InCopy is installed with version 21.0 or any version earlier than 20.5.1, and a user could be tricked into opening a malicious file.

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 20.5.1 or later
Fixed in 20.5.1
Interim mitigation

Update InCopy to the latest version available from Adobe. Avoid opening files from untrusted or unknown sources until the patch is applied, as exploitation requires user interaction.

Recommended fix High confidence

InCopy 20.5.1 or later (for versions before 21.0); InCopy 21.1 or later (for version 21.0)

  1. 1. Close Adobe InCopy if it is currently running
  2. 2. Back up any important InCopy documents and preferences
  3. 3. Open Adobe Creative Cloud desktop application or navigate to helpx.adobe.com/incopy/release-note.html
  4. 4. Locate InCopy in the available applications list
  5. 5. Click Install or Update to install the latest version of InCopy
  6. 6. Wait for the installation to complete
  7. 7. Verify the installed version by opening InCopy and checking Help > About InCopy
Caveat Minimal risk - Adobe incremental updates typically maintain backward compatibility with documents and workflows

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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