HIGH 7.8

CVE-2026-57245: Foxit PDF Editor & Reader Use-After-Free Denial-of-Service

A flaw in Foxit PDF Editor and Foxit PDF Reader allows malicious PDF files to crash the application. When these applications process a PDF with specially crafted hyperlink annotation relationships, they fail to properly validate the annotation structure. This causes internal objects to become corrupted, and when the application closes or cleans up resources, an invalid memory write occurs, crashing the program. An attacker can exploit this by crafting a malicious PDF and delivering it to a user.

Source data · NVD / CISA · public domain

CVSS
3.1 · 7.8 HIGH · CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H
Weaknesses (CWE)
CWE-416
Affected products
3 configuration(s)
Published / Modified
2026-07-08 / 2026-07-09

NVD description (verbatim)

When the application opens a PDF, traverses and builds the annotation elements related to hyperlinks, it fails to validate the abnormal annotation relationships and field combinations. This results in the internal objects entering an invalid state. Eventually, during the destruction phase, an invalid pointer write occurred, causing the application to crash.

1 reference(s) · View on NVD →

SEC.co analysis · AI-assisted, reviewed against source

Technical summary

CVE-2026-57245 is a use-after-free vulnerability (CWE-416) affecting Foxit PDF Editor and Foxit PDF Reader. The vulnerability stems from insufficient validation of PDF annotation relationships and field combinations during hyperlink annotation processing. When a PDF with malformed annotation elements is opened, the application fails to sanitize these objects, leading to an invalid internal state. During resource cleanup and object destruction, an invalid pointer write is triggered, resulting in application termination. The vulnerability is reachable through user interaction (opening a PDF) without requiring elevated privileges.

Business impact

This vulnerability poses a denial-of-service risk to organizations relying on Foxit PDF tools for document processing and review. While it does not enable data theft or system compromise, the crash can disrupt workflows and productivity. More critically, the underlying memory corruption could potentially be weaponized by skilled attackers; the current manifestation as a crash may mask deeper exploitation potential. Organizations should treat this as a priority remediation item given Foxit's prevalence in regulated industries and the ease of delivery via email or file-sharing mechanisms.

Affected systems

The vulnerability affects Foxit PDF Editor and Foxit PDF Reader on Microsoft Windows systems. Both consumer and enterprise editions of these products are in scope. Users on other operating systems (macOS, Linux) should verify patch status with Foxit to confirm whether those versions are also affected. The flaw is triggered only when a user opens a malicious PDF, so air-gapped systems or those with strict PDF handling policies face lower immediate risk.

Exploitability

Exploitability is straightforward and does not require sophisticated technical skills. An attacker needs only to craft a PDF with malformed hyperlink annotation relationships and deliver it to a target user. Social engineering or phishing campaigns could effectively distribute such files. The requirement for user interaction (opening the PDF) is the primary barrier, though this is a low bar in typical business environments where PDF handling is routine. No privilege escalation or network access is required. The CVSS vector (AV:L/AC:L/PR:N/UI:R) reflects these characteristics.

Remediation

Immediate action: Update Foxit PDF Editor and Foxit PDF Reader to the latest patched version available from Foxit's official website. Verify against the vendor advisory to confirm which version number resolves CVE-2026-57245. Interim mitigation: Disable or restrict hyperlink processing in PDFs where possible through application settings. Educate users not to open PDF files from untrusted sources. Consider deploying PDF sandboxing or analysis tools to scan incoming PDFs before they reach end users. Apply the patch to both applications, as the flaw affects both.

Patch guidance

Check Foxit's security advisory and release notes for the specific version number that addresses CVE-2026-57245. Apply patches to all instances of Foxit PDF Editor and Foxit PDF Reader across your environment. Test the patched version in a non-production environment first to ensure compatibility with your workflows and any PDF-dependent integrations. Schedule patch deployment during regular maintenance windows. For enterprise deployments, prioritize systems that handle external or untrusted PDFs first.

Detection guidance

Monitor application crash logs and event viewer entries for Foxit PDF Reader and Foxit PDF Editor terminations. Correlate crashes with specific PDF file characteristics or sources to identify potential attack patterns. Implement endpoint detection and response (EDR) tools to capture process memory states and exception details at crash time. Network-level detection is limited; focus on file integrity monitoring and anomalous PDF receipt patterns. User reporting of unexpected application crashes when opening specific PDFs may be an early indicator of exploitation attempts.

Why prioritize this

Although this vulnerability does not appear on the CISA KEV catalog, it merits immediate attention due to the combination of ease of exploitation, wide user base of affected software, and the memory corruption aspect. The HIGH CVSS score (7.8) reflects multiple privilege paths: confidentiality, integrity, and availability impacts are all marked as high, suggesting the underlying memory issue could be leveraged for more severe attacks. Foxit products are ubiquitous in enterprises, making this a broad-reach risk. Prioritize patching Foxit tools before patching lower-CVSS vulnerabilities in less-exposed applications.

Risk score, explained

The CVSS 3.1 score of 7.8 (HIGH) is justified by multiple factors: the attack vector is local but easily triggered through normal user behavior; attack complexity is low; no privileges are required; and the impact rating is high across all three dimensions (confidentiality, integrity, availability). While the current observable impact is denial-of-service, the use-after-free condition suggests potential for memory disclosure or code execution if the vulnerability is refined. This score appropriately elevates the risk profile above moderate DoS-only flaws.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The attack vector is local (AV:L), meaning the attacker must deliver a malicious PDF file to the victim's system. This is typically done via email, file sharing, or web download. Remote exploitation of the vulnerability itself is not possible; however, remote delivery of the malicious PDF is trivial.

Does this flaw allow an attacker to steal data or execute code?

The current documented manifestation is application crash (denial-of-service). However, the underlying cause is a use-after-free condition, which is a memory safety issue that could potentially be exploited for information disclosure or code execution with additional research and refinement. Organizations should assume the vulnerability poses a higher risk than a simple crash and prioritize patching accordingly.

Which version of Foxit products are affected?

The source data does not specify affected version ranges. Consult Foxit's official security advisory for CVE-2026-57245 to determine which versions are vulnerable and which versions contain the fix. Patch immediately upon availability.

Are macOS and Linux versions of Foxit products affected?

The source data lists Microsoft Windows as an affected vendor/product. Verify with Foxit whether macOS and Linux editions are also vulnerable to this specific flaw, as the memory corruption may be platform-specific or platform-independent.

This analysis is based on publicly disclosed vulnerability data as of July 2026. CVSS scores and severity ratings reflect the vulnerability's technical characteristics at publication; actual risk may vary based on your specific deployment, usage patterns, and compensating controls. Patch version numbers and detailed remediation steps must be verified against the official Foxit security advisory and vendor release notes. This document does not constitute legal or compliance advice. Security teams should validate all guidance in their own environments before production deployment. SEC.co assumes no liability for decisions made based on this intelligence. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).