CVE-2025-54206: Adobe InDesign Desktop · Out-of-bounds Write
Affects Adobe InDesign DesktopSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 26 Oct 2026, 12:55 UTC
- EPSS
- 0.2% chance of exploitation in 30 days – higher than 15% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 12 Aug 2025
Detectable: no evidence on record.
No public nuclei template indexed
Weaponised: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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
| Product | Affected | Fixed in |
|---|---|---|
| Adobe InDesign Desktop | Affected
| Fixed in– |
AI-suggested
Until Adobe releases an official patch, organizations should implement the following mitigations: 1) Educate users to avoid opening InDesign files from untrusted or unknown sources. 2) Employ email and endpoint security solutions to detect and block malicious InDesign files. 3) Use application whitelisting or sandboxing to restrict InDesign's ability to execute arbitrary code or access sensitive system resources. 4) Monitor systems for unusual behavior indicative of exploitation attempts. 5) Maintain regular backups of critical data to enable recovery in case of compromise. 6) Once patches are available, prioritize timely deployment across all affected systems. 7) Consider disabling or restricting InDesign usage on systems where it is not essential to reduce the attack surface.
Description
InDesign Desktop versions 20.4, 19.5.4 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.