Skip to main content
VulnerabilityPublished

CVE-2025-6661: PDF-XChange Editor · Use After Free

Affects PDF-XChange EditorSource CVE Database V5

0

Not known to be exploited · CVSS 7.8 High.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 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 20% of CVEsExploit Prediction Scoring System: the likelihood attackers will use this flaw soon.
CVSS:3.0/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 25 Jun 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
PDF-XChange PDF-XChange EditorAffected
  • =10.5.2.395
Fixed in–

AI-suggested

  1. Immediate mitigation should focus on reducing exposure by restricting the use of PDF-XChange Editor version 10.5.2.395 until a vendor patch is released.
  2. Implement strict email filtering and attachment scanning to block or quarantine suspicious PDF files, especially those from untrusted sources.
  3. Educate users on the risks of opening unsolicited or unexpected PDF attachments and visiting untrusted websites.
  4. Employ application whitelisting and sandboxing techniques to limit the execution context of PDF-XChange Editor, preventing arbitrary code execution from escalating privileges or accessing sensitive resources.
  5. Monitor endpoint behavior for anomalies indicative of exploitation attempts, such as unexpected process spawning or memory corruption indicators.
  6. Use endpoint detection and response (EDR) solutions to detect and respond to suspicious activities related to PDF processing.
  7. Network segmentation should be enforced to contain potential breaches resulting from exploitation.
  8. Maintain up-to-date backups and incident response plans tailored to ransomware or remote code execution scenarios.
  9. Coordinate with the vendor for timely patch deployment once available and verify the integrity of updates before installation.
  10. Consider deploying alternative PDF readers with a better security track record as a temporary measure.

Description

PDF-XChange Editor App Object Use-After-Free Remote Code Execution Vulnerability. This vulnerability allows remote attackers to execute arbitrary code on affected installations of PDF-XChange Editor. User interaction is required to exploit this vulnerability in that the target must visit a malicious page or open a malicious file. The specific flaw exists within the handling of App objects. The issue results from the lack of validating the existence of an object prior to performing operations on the object. An attacker can leverage this vulnerability to execute code in the context of the current process. Was ZDI-CAN-26823.

References

Community reviews

Loading reviews…