dbcve.org
IncopyApplication · Adobe

CVE-2023-26368

HIGH · 7.8 CVSS v3.1 Published 2023-11-16
Fix available
A fix is available. Upgrade to after 18.5 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
Adobe InCopy versions 18.5 (and earlier) and 17.4.2 (and earlier) are affected by 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 · high confidence

Adobe InCopy versions 18.5 and earlier and 17.4.2 and earlier contain an out-of-bounds read vulnerability when parsing crafted files. The vulnerability allows reading past the end of an allocated memory structure, which can potentially be leveraged for arbitrary code execution in the context of the current user. Exploitation requires victim interaction—opening a malicious file.

MitigationUpdate Adobe InCopy to a version newer than 18.5 and 17.4.2. Users should avoid opening files from untrusted sources to mitigate the user-interaction requirement.

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:<= 17.04.2>= 18.0, <= 18.5

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, look for Adobe InCopy in Program Files or Program Files (x86). On macOS, check /Applications for Adobe InCopy. Also check the Windows Registry under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\App Paths\ for InCopy executables.
    Affected if Adobe InCopy is present on the system
  2. Determine the installed version
    On Windows, locate the InCopy executable (INCOPY.exe), right-click, select Properties, then view the Details tab for Product Version. On macOS, right-click the InCopy app in Finder, select Get Info, and read the Version field.
    Affected if Unable to retrieve the product version from the executable or application info
  3. Compare version to affected ranges
    Compare your installed version number to the vulnerable ranges: version 17.4.2 or lower, OR version 18.0 through 18.5. Versions outside these ranges (below 17.0, between 17.4.3 and 17.x, or above 18.5) are not affected.
    Affected if Installed version is 17.4.2 or earlier, OR installed version is 18.0 through 18.5
  4. Verify the attack surface exists
    Confirm that the InCopy application can open files, as exploitation requires a user to open a malicious crafted file using InCopy.
    Affected if InCopy can open files and users may open files from untrusted sources

The environment is affected if Adobe InCopy is installed with a version between 17.4.2 and earlier, or between 18.0 and 18.5 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 a release after 18.5
Interim mitigation

Update Adobe InCopy to a version newer than 18.5 and 17.4.2. Users should avoid opening files from untrusted sources to mitigate the user-interaction requirement.

Recommended fix Moderate confidence

Adobe InCopy 18.5.1 or later (18.x series); Adobe InCopy 17.4.3 or later (17.x series) - upgrade to latest available version

  1. 1. Open Adobe Creative Cloud desktop application or navigate to the Adobe InCopy download page
  2. 2. Check the current installed version of InCopy by launching the application and going to Help > About InCopy
  3. 3. If running version 17.4.2 or earlier, or versions 18.0 through 18.5, an update is required
  4. 4. In Adobe Creative Cloud, navigate to the Apps tab and locate Adobe InCopy
  5. 5. Click the Update button next to InCopy to download and install the latest version
  6. 6. Alternatively, manually download the latest InCopy version from helpx.adobe.com or the Adobe Creative Cloud website
  7. 7. After installation, verify the new version by checking Help > About InCopy
Caveat Standard Adobe update - minimal risk; ensure any linked documents are backed up before updating

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

Fix this in Incopy Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing4.0 h
  • Review / QA2.0 h
15.0 hours of engineering $2,640
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,224.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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