Skip to main content
VulnerabilityPublished Updated

CVE-2025-54223: Adobe InCopy · Use After Free

Affects Adobe InCopySource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.1 base score
7.8High
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.2% chance of exploitation in 30 days – higher than 21% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 12 Aug 2025

  2. Detectable: no evidence on record.

    No public nuclei template indexed

  3. Weaponised: no evidence on record.

    No public exploit code indexed in Metasploit or Exploit-DB

  4. Exploited in the wild: no evidence on record.

    Not in CISA KEV and no source reports exploitation

  5. Observed by OffSeq Mirage: no evidence on record.

    No attack traffic recorded by OffSeq Mirage sensors

A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 26 Oct 2026.

What to do

Affected software

ProductAffectedFixed in
Adobe InCopyAffected
  • =0
Fixed in–

AI-suggested

  1. Immediately restrict the opening of InCopy files from untrusted or unknown sources to reduce exposure to malicious documents.
  2. Implement strict email filtering and attachment scanning to detect and block potentially malicious InCopy files.
  3. Employ application whitelisting to prevent unauthorized execution of code spawned by malicious files.
  4. Use endpoint detection and response (EDR) tools to monitor for suspicious behavior related to InCopy processes and memory usage anomalies.
  5. Educate users about the risks of opening unsolicited or unexpected InCopy files and encourage verification of file sources.
  6. Regularly back up critical data and maintain offline copies to mitigate potential data loss from exploitation.
  7. Monitor Adobe’s official channels for patches or updates and apply them promptly once available.
  8. Consider sandboxing or running InCopy in isolated environments to limit the impact of potential exploitation.
  9. Review and tighten user privileges to minimize the damage scope if exploitation occurs.
  10. Conduct threat hunting exercises focusing on indicators of compromise related to InCopy file handling.

Description

InCopy versions 20.4, 19.5.4 and earlier are affected by a Use After Free 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.

References

Community reviews

Loading reviews…