What is the CVSS score of CVE-2026-57252?

CVE-2026-57252 has a CVSS 3.1 base score of 7.8 (High). CVSS vector: CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H. EPSS exploitation probability: 0.1%.

Which versions of Foxit PDF Reader are affected by CVE-2026-57252?

Foxit PDF Reader and Editor contain a use-after-free vulnerability (CVSS 7.8) enabling application crashes and potential code execution when users open malicious PDF files with embedded JavaScript.

How to fix or mitigate CVE-2026-57252?

Within 24 hours: identify all Foxit PDF Reader and Editor deployments and disable JavaScript execution in application preferences. Within 7 days: implement policies restricting PDF opening to trusted sources only and evaluate alternative PDF readers for critical workflows. Within 30 days: monitor Foxit security advisories for patch availability and prepare rapid deployment procedures.

Foxit PDF Reader CVE-2026-57252

EUVD-2026-42200 HIGH

Use After Free (CWE-416)

2026-07-08 Foxit

GHSA-9428-wgmv-2fjj

Memory Corruption Denial Of Service Use After Free Foxit Pdf Editor Foxit Pdf Reader

7.8

CVSS 3.1 · Vendor: Foxit

Severity by source

Vendor (Foxit) PRIMARY

7.8 HIGH

AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

vuln.today AI

7.8 HIGH

Local file-open vector (AV:L/UI:R) with no privileges (PR:N); UAF plausibly yields code execution so C/I/A retained High, though the description alone shows only a crash.

3.1 AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H

4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Primary rating from Vendor (Foxit).

CVSS VectorVendor: Foxit

Attack Vector

Local

Attack Complexity

Low

Privileges Required

None

User Interaction

Required

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Lifecycle Timeline

Analysis Generated

Jul 08, 2026 - 08:56 vuln.today

DescriptionCVE.org

When the application opens a PDF file, during the process of JavaScript deleting pages and removing attachment annotations, it will cause the attachment panel to continue accessing invalid pointers, eventually leading to the application crashing.

AnalysisAI

Use-after-free memory corruption in Foxit PDF Reader and Foxit PDF Editor allows a crafted PDF to crash the application when its embedded JavaScript deletes pages and removes attachment annotations while the attachment panel still references freed pointers. A victim must open the malicious document (UI:R), and no public exploit has been identified at time of analysis. Although the reported behavior is an application crash, Foxit's own CVSS scoring rates confidentiality, integrity, and availability all High, implying potential for code execution beyond denial of service.

Technical ContextAI

The flaw is a CWE-416 Use-After-Free in the PDF viewer's document/attachment handling. Foxit supports embedded JavaScript (a subset of the Adobe/Acrobat JS API) that can programmatically manipulate document structure, including deleting pages and removing annotations. When JavaScript deletes pages and removes attachment annotations, the objects backing those attachments are freed, but the attachment panel UI continues to dereference the now-dangling pointers. The affected products per CPE are cpe:2.3:a:foxit_software_inc.:foxit_pdf_editor and cpe:2.3:a:foxit_software_inc.:foxit_pdf_reader, both desktop PDF applications that render and execute document content locally.

RemediationAI

Apply the vendor update from the Foxit security bulletin at https://www.foxit.com/support/security-bulletins.html; a specific fixed version is not included in the provided data, so consult that advisory for the exact patched release and upgrade both Foxit PDF Reader and Foxit PDF Editor to it. As a compensating control until patched, disable JavaScript execution in Foxit (Preferences > JavaScript > uncheck 'Enable JavaScript Actions'), which prevents the malicious script from triggering the page-deletion/annotation-removal sequence at the cost of breaking legitimate form and interactive-PDF functionality. Additionally, avoid opening PDFs from untrusted sources and enable Safe Reading Mode / sandboxing where available to reduce the impact of memory corruption.