dbcve.org
IncopyApplication · Adobe

CVE-2026-34707

HIGH · 7.8 CVSS v3.1 Published 2026-06-09
Fix available
A fix is available. Upgrade to 20.5.4 / 21.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 21.3, 20.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 21.3, 20.5.3 and earlier contain a heap-based buffer overflow vulnerability that can be triggered when a user opens a malicious file. Successful exploitation allows arbitrary code execution in the context of the current user.

MitigationUpdate to the latest version of InCopy released by Adobe. Avoid opening untrusted or unexpected InCopy files until the patch 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:< 20.5.4>= 21.0, < 21.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 for InCopy in the installed programs list via Control Panel > Programs and Features, or look for the InCopy executable at typical paths like C:\Program Files\Adobe\Adobe InCopy 202x\InCopy.exe or C:\Program Files (x86)\Adobe\Adobe InCopy 202x\InCopy.exe. On macOS, check /Applications/ for Adobe InCopy.app.
    Affected if InCopy is present on the system
  2. Determine the installed InCopy version number
    On Windows, right-click the InCopy executable, select Properties, then go to the Details tab to view the File Version. On macOS, right-click Adobe InCopy.app, select Get Info, and look under Version in the General section. Alternatively, open InCopy and go to Help > About InCopy.
    Affected if The displayed version is < 20.5.4 OR >= 21.0 and < 21.4
  3. Confirm vulnerability trigger condition is present
    This vulnerability requires a victim to open a specially crafted malicious file. Check recent files opened by InCopy if you suspect targeted exposure, but the vulnerability is inherent to the software version itself when parsing certain file types.
    Affected if The affected version is running and would process a maliciously crafted file

A user is affected if Adobe InCopy is installed and its version falls below 20.5.4 or is between 21.0 and 21.3 inclusive.

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

Update to the latest version of InCopy released by Adobe. Avoid opening untrusted or unexpected InCopy files until the patch is applied.

Recommended fix High confidence

InCopy 20.5.4 (for 20.x branch) or InCopy 21.4 (for 21.x branch)

  1. 1. Determine the currently installed Adobe InCopy version by opening InCopy and navigating to Help > About InCopy
  2. 2. If running version 20.x (20.5.3 or earlier), upgrade to InCopy version 20.5.4 or later
  3. 3. If running version 21.0 through 21.3, upgrade to InCopy version 21.4 or later
  4. 4. Download the appropriate fixed version from the official Adobe website (helpx.adobe.com) or through the Creative Cloud desktop application
  5. 5. Close all Adobe applications before installing the update
  6. 6. Run the installer and follow the on-screen prompts to complete the installation
  7. 7. After installation, verify the version by checking Help > About InCopy to confirm the update was successful
Caveat Standard Adobe update - minimal breaking changes expected for minor version upgrades; ensure compatibility with existing workflows and plug-ins

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-2026-34707 — 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-34707 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