Skip to main content
VulnerabilityPublished

CVE-2024-8824: PDF-XChange Editor · Out-of-bounds Read

Affects PDF-XChange EditorSource CVE Database V5

0

Not known to be exploited · CVSS 3.3 Low.

Data as of 26 Oct 2026, 14:05 UTC

CVSS 3.0 base score
3.3Low
How severe the flaw is on the 0–10 CVSS scale.
EPSS
0.3% chance of exploitation in 30 days – higher than 27% 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:L/I:N/A:N

Exploitation evidence

  1. Disclosed: evidence found.

    CVE published 22 Nov 2024

  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.3.0.386
Fixed in–

AI-suggested

To mitigate CVE-2024-8824, organizations should implement several specific measures beyond generic advice: 1) Restrict or monitor the use of PDF-XChange Editor version 10.3.0.386, especially for opening PDFs from untrusted or external sources. 2) Employ application whitelisting and sandboxing techniques to isolate PDF-XChange Editor processes, limiting the impact of potential exploitation. 3) Use network-level protections such as email filtering and web content scanning to detect and block malicious PDF files before reaching end users. 4) Educate users about the risks of opening unsolicited or suspicious PDF attachments and encourage verification of file sources. 5) Monitor vendor communications closely for patches or updates addressing this vulnerability and apply them promptly once available. 6) Consider deploying endpoint detection and response (EDR) solutions capable of identifying anomalous behavior related to PDF parsing or memory access violations. 7) Where feasible, evaluate alternative PDF viewers with a stronger security track record or more frequent updates. These targeted steps help reduce the risk of exploitation while maintaining operational continuity.

Description

PDF-XChange Editor JB2 File Parsing Out-Of-Bounds Read Information Disclosure Vulnerability. This vulnerability allows remote attackers to disclose sensitive information 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 parsing of JB2 files. The issue results from the lack of proper validation of user-supplied data, which can result in a read past the end of an allocated object. An attacker can leverage this in conjunction with other vulnerabilities to execute arbitrary code in the context of the current process. Was ZDI-CAN-24262.

References

Community reviews

Loading reviews…