dbcve.org
IncopyApplication · Adobe

CVE-2026-34631

HIGH · 7.8 CVSS v3.1 Published 2026-04-14
Fix available
A fix is available. Upgrade to 20.5.3 / 21.3 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.5.2, 21.2 and earlier are affected by an out-of-bounds write 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 20.5.2, 21.2 and earlier contain an out-of-bounds write vulnerability that can be triggered by opening a maliciously crafted file, leading to arbitrary code execution in the context of the current user.

MitigationUpdate InCopy to the latest patched version. Avoid opening untrusted or unexpected files from unverified 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:< 20.5.3>= 21.0, < 21.3

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 for InCopy in Program Files or look in the registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\InCopy.exe. On macOS, check /Applications for Adobe InCopy.
    Affected if InCopy is not installed on the system
  2. Find the installed InCopy version number
    On Windows, right-click the InCopy executable (usually in C:\Program Files\Adobe\Adobe InCopy 202X or similar), select Properties, and view the Details tab for the Product Version. On macOS, right-click Adobe InCopy in Applications, select Get Info, and view the Version field.
    Affected if Unable to determine the version number
  3. Compare your version against affected ranges
    The affected versions are: 20.5.2 and earlier (any version < 20.5.3 in the 20.x line), and versions 21.0 through 21.2 (any version >= 21.0 but < 21.3). Compare your installed version to these ranges.
    Affected if Installed version falls within < 20.5.3 or >= 21.0 and < 21.3
  4. Verify if the vulnerability trigger condition exists
    This vulnerability requires opening a specially crafted file. Check whether users in your environment commonly open files from untrusted or unknown sources, as this is required for exploitation.
    Affected if Users routinely open files from untrusted or unknown sources

You are affected if Adobe InCopy is installed and the installed version is less than 20.5.3, or is version 21.0 through 21.2.

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.3 / 21.3 or later
Fixed in 20.5.321.3
Interim mitigation

Update InCopy to the latest patched version. Avoid opening untrusted or unexpected files from unverified sources.

Recommended fix High confidence

InCopy 20.5.3 or InCopy 21.3 (or later)

  1. 1. Open Adobe InCopy and go to Help > About InCopy to confirm current installed version
  2. 2. If running version 20.5.2 or earlier, or version 21.0-21.2, an update is required
  3. 3. Update via Adobe Creative Cloud desktop app: Open CC app, find InCopy in the Apps tab, click Update
  4. 4. Alternatively, download the fixed version directly from helpx.adobe.com
  5. 5. After installation, verify the version is 20.5.3 or 21.3 or later via Help > About InCopy
Caveat Standard Adobe update; ensure Creative Cloud account is active for seamless updates

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

Fix this in Incopy Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing2.0 h
  • Review / QA2.0 h
16.0 hours of engineering $2,900
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,640.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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