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

CVE-2026-57251 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 Editor are affected by CVE-2026-57251?

Foxit PDF Editor and Reader are vulnerable to denial-of-service attacks via specially crafted PDF files, creating business continuity and productivity risk for any organization relying on these tools…

How to fix or mitigate CVE-2026-57251?

Within 24 hours: Inventory all Foxit PDF Editor and Reader deployments; restrict opening PDFs from untrusted external sources and communicate the vulnerability to users. Within 7 days: Deploy email gateway rules to flag or block PDF attachments from external domains; conduct security awareness training on malicious PDF risks. Within 30 days: Monitor Foxit's advisory channels for patch release; begin evaluating alternative PDF readers (Adobe Reader DC, open-source alternatives) as migration candidates.

Foxit PDF Editor CVE-2026-57251

EUVD-2026-42203 HIGH

Improper Validation of Array Index (CWE-129)

2026-07-08 Foxit

GHSA-vj42-9r5c-37wj

Denial Of Service 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

5.5 MEDIUM

Local file open with user interaction (AV:L/UI:R/PR:N); documented impact is a crash only, so A:H with C:N/I:N rather than the input's inflated C:H/I:H.

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

4.0 AV:L/AC:L/AT:N/PR:N/UI:A/VC:N/VI:N/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:57 vuln.today

DescriptionCVE.org

The application opens a PDF, but the cloud-like appearance of the construction process lacks proper setting of an upper limit and consistency checks. Out-of-bounds access to the underlying array is exposed, ultimately leading to a crash of the application.

AnalysisAI

Denial of service in Foxit PDF Editor and Foxit PDF Reader arises when the application renders a PDF containing cloud-style annotation/border appearances, because the code that builds that geometry omits an upper-bound limit and consistency checks. A local attacker who convinces a user to open a malicious PDF can trigger an out-of-bounds array access that crashes the application; no public exploit has been identified at time of analysis and the flaw is not listed in CISA KEV. Although the NVD vector claims high confidentiality and integrity impact, the vendor description and tags describe only a crash.

Technical ContextAI

The affected component is the PDF appearance-stream construction logic in Foxit's shared rendering engine (cpe:2.3:a:foxit_software_inc.:foxit_pdf_editor and cpe:2.3:a:foxit_software_inc.:foxit_pdf_reader), specifically the routine that generates the 'cloud' (cloudy) visual effect used for cloud-shaped rectangles/polygons in markup annotations. The root cause is CWE-129 (Improper Validation of Array Index): a count or index derived from attacker-controlled PDF data is used to walk an underlying array without validating it against the array's real bounds and without a sanity/upper-limit check, so a crafted value drives reads or writes past the allocation. This is a classic memory-safety defect in native PDF parsers where object dictionaries and appearance parameters are trusted for sizing.

RemediationAI

Update Foxit PDF Editor and Foxit PDF Reader to the fixed build listed in Foxit's security advisory; a patch is available per vendor advisory at https://www.foxit.com/support/security-bulletins.html, though an exact fix version was not provided in this data and should be taken directly from that bulletin. Until patched, reduce exposure by not opening PDFs from untrusted sources and by enabling/keeping Foxit's Safe Reading Mode, which restricts risky content processing (trade-off: some interactive PDF features may be limited); where feasible, open untrusted documents in a sandboxed or non-persistent environment so a crash cannot be leveraged for further impact. Because exploitation requires a user to open a file, user-awareness and mail/web attachment filtering are effective compensating controls with minimal operational side effects.