CVE-2026-27287
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 20.5.2, 21.2 and earlier are affected by an out-of-bounds read vulnerability when parsing a crafted file, which could result in a read past the end of an allocated memory structure. An attacker could leverage this vulnerability to execute code 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 · moderate confidenceAn out-of-bounds read vulnerability exists in Adobe InCopy when parsing crafted files. The vulnerability allows reading past the end of allocated memory structures, potentially enabling arbitrary code execution in the context of the current user. Exploitation requires user interaction via opening a 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.3>= 21.0, < 21.3CVSS 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.
-
Locate Adobe InCopy installationOn Windows, check C:\Program Files\Adobe\Adobe InCopy 2024 or C:\Program Files\Adobe\Adobe InCopy 2025. On macOS, check /Applications/Adobe InCopy 2024 or /Applications/Adobe InCopy 2025.Affected if InCopy is installed in any version
-
Determine installed InCopy versionOn Windows, open Registry Editor and navigate to HKLM\SOFTWARE\Adobe\InCopy\Version (or HKLM\SOFTWARE\WOW6432Node\Adobe\InCopy\Version). On macOS, right-click Adobe InCopy in Applications, select Get Info, and note the version number.Affected if Version number cannot be determined or is not visible
-
Compare version against affected rangesIf version starts with 20.x, check if it is below 20.5.3. If version starts with 21.x, check if it is 21.0, 21.1, or 21.2. Compare your installed version to these thresholds.Affected if Installed version is 20.x less than 20.5.3, OR installed version is 21.0 through 21.2 (inclusive)
-
Confirm file parsing features are in useThis vulnerability is triggered when opening specially crafted files. Check if users routinely open external .icml, .icmt, or other InCopy file formats from untrusted sources.Affected if Users open InCopy files from email attachments or untrusted sources without prior scanning
You are affected if Adobe InCopy is installed and the version number falls below 20.5.3 for 20.x releases, or between 21.0 and 21.2 for 21.x releases.
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.321.3
Update InCopy to the patched version once released (versions beyond 21.2). Implement user awareness training to avoid opening untrusted files, and consider disabling file preview thumbnails in enterprise environments.
InCopy 20.5.3 or later; InCopy 21.3 or later
- 1. Close any running instances of Adobe InCopy
- 2. Open Adobe Creative Cloud desktop application or navigate to Adobe's website
- 3. Locate Adobe InCopy in your installed applications
- 4. Check the current version by opening InCopy and going to Help > About InCopy
- 5. If running version 20.5.2 or earlier, upgrade to version 20.5.3 or later
- 6. If running version 21.0, 21.1, or 21.2, upgrade to version 21.3 or later
- 7. Verify the installation completed successfully and confirm the new version number
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation4.0 h
- Implementation2.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,152.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-27287 — 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-27287 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