CVE-2025-54229: Adobe Framemaker · Use After Free
Affects Adobe FramemakerSource 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 12% 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 Adobe Framemaker | Affected
| Fixed in– |
AI-suggested
Organizations should implement the following specific mitigations: 1) Monitor Adobe’s security advisories closely and apply patches immediately once released. 2) Restrict Framemaker file handling by disabling automatic opening of files from untrusted sources or email attachments. 3) Employ application whitelisting to limit execution of unauthorized code. 4) Educate users about the risks of opening unsolicited or suspicious Framemaker files. 5) Use endpoint detection and response (EDR) tools to monitor for suspicious behavior related to Framemaker processes. 6) Consider sandboxing Framemaker or running it in a restricted environment to limit the impact of potential exploitation. 7) Regularly back up critical documentation to enable recovery in case of compromise. These measures go beyond generic advice by focusing on controlling file sources, user behavior, and runtime environment hardening.
Description
Adobe Framemaker versions 2020.8, 2022.6 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.