CVE-2026-57240: Foxit PDF Editor · Use After Free
Affects Foxit PDF EditorSource CVE Database V5
Not known to be exploited · CVSS 7.8 High.
Data as of 21 Nov 2026, 17:35 UTC
- EPSS
- 0.1% chance of exploitation in 30 days – higher than 8% 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:HExploitation evidence
Disclosed: evidence found.
CVE published 8 Jul 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by 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 21 Nov 2026.
What to do
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| Foxit Software Inc.Foxit PDF Editor | Affected
| Fixed in– |
| Foxit Software Inc.Foxit PDF Reader | Affected
| Fixed in– |
AI-suggested
Until an official fix is released, users should exercise caution when opening PDF files containing JavaScript from untrusted sources and consider disabling JavaScript execution in the application if possible.
Description
When the application opens a PDF file and JavaScript deletes the PDF fields, the subsequent logic still uses the old field pointers, resulting in invalid pointer references and causing the application to crash.