CVE-2026-34706
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 · uneditedInCopy versions 21.3, 20.5.3 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 confidenceAdobe InCopy versions 21.3, 20.5.3 and earlier contain an out-of-bounds write vulnerability that allows memory corruption beyond allocated buffers. Successful exploitation enables arbitrary code execution in the context of the current user, but requires the victim to open a specially crafted malicious file.
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< 20.5.4>= 21.0, < 21.4CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Verify InCopy is installedCheck for InCopy.exe in typical installation paths such as C:\Program Files\Adobe\Adobe InCopy 2024\ or C:\Program Files\Adobe\Adobe InCopy 2023\, or search for the executable using 'where InCopy' in Command PromptAffected if InCopy.exe is found on the system
-
Identify installed InCopy versionRight-click InCopy.exe, select Properties, then the Details tab to view the File Version, or use the command 'InCopy.exe --version' in the installation directoryAffected if The displayed version cannot be determined or is less than 20.5.4 or between 21.0 and 21.3.x inclusive
-
Compare version against affected rangesThe affected versions are: 20.5.3 and earlier, OR 21.0 through 21.3. If your version is 20.5.4 or higher, OR 21.4 or higher, it is NOT affected. Otherwise, it IS affectedAffected if Installed version is < 20.5.4 (such as 20.5.3 or earlier) OR is >= 21.0 but < 21.4 (such as 21.0, 21.1, 21.2, or 21.3)
-
Confirm the attack surfaceThe vulnerability is triggered when a user opens a malicious file in InCopy. Check if users have the ability to open files from untrusted sourcesAffected if Users routinely open files from untrusted or unknown sources in InCopy
The environment is affected if Adobe InCopy is installed and the installed version falls below 20.5.4 or is between 21.0 and 21.3.x inclusive.
Generated from the published advisory. Verify against your own configuration.
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 · scoped20.5.421.4
Update InCopy to the latest patched version provided by Adobe. As a defense-in-depth measure, enforce user training to avoid opening untrusted files and consider application whitelisting to mitigate risks from malicious documents.
InCopy 20.5.4 or later for 20.x branch; InCopy 21.4 or later for 21.x branch
- Close Adobe InCopy if currently running
- Back up any important InCopy documents before updating
- Download Adobe InCopy version 20.5.4 or later (for 20.x line) OR version 21.4 or later (for 21.x line) from the official Adobe website at helpx.adobe.com
- Run the downloaded installer and follow the on-screen prompts to complete the upgrade
- After installation, verify the updated version by opening InCopy and checking Help > About InCopy
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-34706 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-34706 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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