HIGH 7.8

CVE-2026-13129: Use-After-Free in Foxit PDF Editor & Reader Causes Denial of Service

A vulnerability in PDF processing applications allows attackers to crash the program by crafting a malicious PDF file with a corrupted field tree structure. When the application opens the file and JavaScript attempts to access form fields, it ends up holding a reference to an invalid object, eventually causing the application to read from an invalid memory location and crash. This is a local attack that requires user interaction—the victim must open the malicious PDF—but successful exploitation denies service and could mask further system compromise attempts.

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 file, JavaScript uses the damaged field tree to trigger field traversal, resulting in the program holding an invalid form object when accessing the field property path. Eventually, the application crashes due to reading an invalid pointer.

1 reference(s) · View on NVD →

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

Technical summary

CVE-2026-13129 is a use-after-free vulnerability (CWE-416) affecting PDF readers and editors. The root cause is improper validation of the PDF field tree structure. When JavaScript in the PDF processes field properties through a damaged tree, the application retains a stale object reference. Subsequent pointer dereference operations cause a NULL or invalid pointer read, triggering an unhandled exception. The vulnerability exists in the PDF parsing and JavaScript execution layers, affecting Foxit PDF Editor, Foxit PDF Reader, and Microsoft Windows environments where these applications run.

Business impact

This vulnerability enables denial of service attacks against users and organizations relying on PDF processing. An attacker can distribute a weaponized PDF that crashes the victim's application or system when opened. For organizations using Foxit products for secure document workflows, this could disrupt operations. Additionally, a crash event may indicate active exploitation attempts, warranting incident investigation. While the current reported impact is availability (crash), the high CVSS score reflects the potential for escalation in environments where the crash corrupts shared memory or triggers additional memory safety violations.

Affected systems

Foxit PDF Editor and Foxit PDF Reader are the primary affected products. The vulnerability also affects Microsoft Windows, likely because Windows is the execution environment and its memory management behavior influences exploitation. Verify exact version boundaries against Foxit's official security advisory; patch availability varies by product line (Editor vs. Reader) and release branch.

Exploitability

Exploitability is moderate to high. The attack requires local file access and user interaction (opening a PDF), which are common scenarios in office and knowledge-work environments. No special privileges are required to trigger the crash. The CVSS vector AV:L/AC:L/PR:N/UI:R indicates low complexity and no privilege escalation prerequisite. The vulnerability is not currently tracked in the CISA KEV catalog, suggesting active exploitation has not been widely observed; however, the simplicity of crafting a malicious PDF makes opportunistic attacks probable.

Remediation

Organizations should prioritize patching Foxit PDF Editor and Foxit PDF Reader installations. Consult Foxit's security advisories to identify patched versions and deploy updates through your standard patch management process. For Microsoft Windows, apply any available cumulative updates relevant to PDF handling. Interim mitigations include restricting PDF file access from untrusted sources, disabling JavaScript execution in PDF readers if the application permits, and educating users not to open unsolicited PDF files.

Patch guidance

Contact Foxit for the specific patched versions of PDF Editor and PDF Reader that address CVE-2026-13129. Verify patch version numbers in the official Foxit security advisory before deployment. Microsoft Windows patches, if applicable, should be deployed as part of your regular patch cycle. Test patches in a non-production environment first to ensure compatibility with existing workflows.

Detection guidance

Monitor application crash logs and Windows Event Viewer for unexpected termination of Foxit PDF Editor or PDF Reader processes, particularly when correlated with file access events. Endpoint Detection and Response (EDR) solutions can flag suspicious PDF file creation or distribution. Network-level detection is limited since the attack is local; focus on endpoint telemetry. Consider implementing file integrity monitoring on shared PDF repositories to detect malicious modifications or unusual file creation timestamps.

Why prioritize this

This vulnerability merits high priority due to its high CVSS score (7.8), simplicity of exploitation, and widespread use of Foxit products in enterprise environments. The crash condition, while not enabling data exfiltration directly, can mask other attacks or be used for sabotage. Rapid patching across Foxit deployments is recommended to reduce the window of exposure, especially in organizations receiving PDFs from external parties.

Risk score, explained

The CVSS 3.1 score of 7.8 (HIGH) reflects the combination of local attack vector, low attack complexity, no privilege requirement, and user interaction (opening a PDF). The impact assessment covers all three pillars—confidentiality, integrity, and availability—reflecting that a crash can corrupt in-memory state, potentially exposing sensitive document content before termination, and denying service. The score does not presume remote exploitation; it is bounded to local scenarios.

Frequently asked questions

Can this vulnerability be exploited remotely?

No. The vulnerability requires local file access and user interaction. An attacker could distribute a malicious PDF via email or a website, but exploitation occurs only when the victim's application opens it locally. The CVSS vector AV:L confirms this is a local attack vector.

Does the crash expose sensitive data?

The vulnerability itself is a use-after-free condition that leads to a crash, not a controlled memory read. However, in the moments before the crash, in-memory document content may be accessed, and depending on memory layout, some data could theoretically be exposed. The safest assumption is to treat any crash as a potential information disclosure event and investigate the context.

Are Foxit Reader and Foxit Editor both affected?

Yes, both products are listed as affected. However, patch versions, deployment methods, and availability timelines may differ between them. Verify the specific version ranges in Foxit's official security bulletin before assuming one patch applies to both.

What should we do if we have PDFs from untrusted sources?

Isolate them in a sandboxed or quarantined environment. If possible, convert them to another format using a specialized service (not the vulnerable application), or review the PDF in a read-only, minimal-functionality viewer. Until patches are deployed, avoid opening PDFs from external sources with Foxit applications.

This analysis is based on the CVE-2026-13129 vulnerability record and publicly available descriptions as of the publication date. Patch version numbers, affected product versions, and official mitigation guidance should be verified against Foxit's official security advisory and vendor statements. This document does not constitute a substitute for vendor guidance. Organizations should conduct their own risk assessment and testing before deploying patches. SEC.co makes no warranty regarding the completeness or accuracy of this analysis and recommends consulting with your security team and affected vendors for definitive remediation steps. Source: NVD (public-domain), retrieved 2026-08-17. Analysis generated by SEC.co (claude-haiku-4-5).