Skip to main content
VulnerabilityPublished Updated

CVE-2025-47121: Adobe Framemaker · Access of Uninitialized Pointer

Affects Adobe FramemakerSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 09:15 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 13% 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 8 Jul 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 Adobe FramemakerAffected
  • =0
Fixed in–

AI-suggested

Organizations should implement the following specific mitigations: 1) Immediately restrict the opening of Framemaker files from untrusted or unknown sources, using email filtering and endpoint controls to block suspicious attachments. 2) Educate users on the risks of opening unsolicited or unexpected Framemaker documents, emphasizing cautious handling of files from external parties. 3) Employ application whitelisting and sandboxing techniques to limit Framemaker's ability to execute arbitrary code or access critical system resources. 4) Monitor systems for unusual Framemaker process behavior or unexpected network activity that could indicate exploitation attempts. 5) Maintain up-to-date backups of critical documentation to recover from potential data corruption or ransomware attacks. 6) Coordinate with Adobe for timely patch deployment once official fixes become available, and test patches in controlled environments before widespread rollout. 7) Consider deploying endpoint detection and response (EDR) solutions capable of detecting exploitation patterns related to memory corruption vulnerabilities. These measures go beyond generic advice by focusing on controlling file sources, user awareness, and proactive detection tailored to Framemaker's usage context.

Description

Adobe Framemaker versions 2020.8, 2022.6 and earlier are affected by an Access of Uninitialized Pointer 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…