Skip to main content
CVE-2025-54231VulnerabilityPublished Updated

CVE-2025-54231: Adobe Framemaker · Use After Free

Affects Adobe FramemakerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 06:26 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 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: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 2026-10-26.

What to do

Affected software

ProductAffectedFixed in
Adobe Adobe FramemakerAffected
  • =0
Fixed in–

AI-suggested

1. Monitor Adobe's official channels for patches and apply updates promptly once available to remediate the vulnerability. 2. Until patches are released, implement strict controls on the receipt and opening of Framemaker files, including blocking or quarantining files from untrusted sources. 3. Educate users about the risks of opening unsolicited or suspicious Framemaker documents and encourage verification of file origins. 4. Employ endpoint detection and response (EDR) solutions to monitor for anomalous behavior indicative of exploitation attempts, such as unexpected process execution or memory manipulation. 5. Restrict Framemaker usage to trusted environments and consider sandboxing or running the application with least privilege to limit potential damage. 6. Use network segmentation to isolate systems running Framemaker from critical infrastructure to reduce lateral movement opportunities. 7. Maintain regular backups of critical data and documentation to enable recovery in case of compromise. 8. Review and tighten email filtering and attachment scanning policies to detect and block malicious Framemaker files.

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.

References

Community reviews

Loading reviews…