Skip to main content
CVE-2025-54232VulnerabilityPublished Updated

CVE-2025-54232: 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

To mitigate CVE-2025-54232, organizations should implement the following specific measures: 1) Monitor Adobe's official channels for patches and apply updates promptly once released. 2) Restrict Framemaker file sources by enforcing strict email and file download policies to prevent opening files from untrusted or unknown origins. 3) Employ application whitelisting and sandboxing techniques to limit Framemaker's ability to execute arbitrary code or access sensitive system resources. 4) Educate users on the risks of opening unsolicited or suspicious Framemaker files and implement security awareness training focused on social engineering. 5) Utilize endpoint detection and response (EDR) solutions to detect anomalous behavior related to Framemaker processes. 6) Consider network segmentation to isolate systems running Framemaker, reducing potential lateral movement if compromised. 7) Regularly back up critical documentation and systems to enable recovery in case of compromise. These targeted mitigations go beyond generic advice by focusing on controlling file trust boundaries, user behavior, and containment strategies specific to Framemaker environments.

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…