dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-57258

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to after 2026.1.1.70276 or later.
See remediation →
64/100
Remediation priority · Elevated
No privileges 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
The PRC file header parsing logic trusts the constructed file structure description information, assumes that the underlying array contains elements and reads them, leading to out-of-bounds reads and application crashes.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · moderate confidence

The PRC file header parsing logic fails to validate that arrays contain elements before accessing them. The code trusts the file structure description information from the constructed header without checking array bounds, leading to out-of-bounds reads that cause application crashes.

MitigationImplement input validation to verify array bounds and element counts before reading from arrays during PRC file header parsing; add checks to ensure the underlying arrays contain expected elements before accessing them.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
Pdf EditorApplication
Affected:<= 13.2.4.24048>= 14.0.0.33046, <= 14.0.4.33508>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.3.0.35737>= 2026.1.0.36452, <= 2026.1.1.36485<= 13.2.3.63444>= 14.0.0.33046, <= 14.0.3.69295>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479>= 2025.1.0.66692, <= 2025.3.0.69570>= 2026.1.0.70169, <= 2026.1.1.70276
Pdf ReaderApplication
Affected:<= 2026.1.1.36485<= 2026.1.1.70276

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Local
Complexity
Low
Privileges
None
User interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
High

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

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Foxit product
    Check Program Files or Program Files (x86) for Foxit PDF Editor or Foxit Reader folders. Also check Windows Registry under HKLM\SOFTWARE\Foxit Software or HKCU\SOFTWARE\Foxit Software for installed Foxit applications.
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is present on the system
  2. Locate the installed version
    Right-click the Foxit executable (e.g., FoxitPDFEditor.exe or FoxitReader.exe), select Properties, and check the Details tab for the Product Version. Alternatively, open Foxit and go to Help > About to view the version.
    Affected if Version cannot be determined or does not match the product naming convention
  3. Compare version against affected ranges for Foxit PDF Editor
    For Foxit PDF Editor versions with the 14.x.x format, check if version <= 13.2.4.24048, OR >= 14.0.0.33046 AND <= 14.0.4.33508, OR >= 2023.1.0.15510 AND <= 2023.3.0.23028, OR >= 2024.1.0.23997 AND <= 2024.4.1.27687, OR >= 2025.1.0.27937 AND <= 2025.3.0.35737, OR >= 2026.1.0.36452 AND <= 2026.1.1.36485. Also check secondary ranges: <= 13.2.3.63444, >= 14.0.0.33046 AND <= 14.0.3.69295, >= 2023.1.0.55583 AND <= 2023.3.0.63083, >= 2024.1.0.63682 AND <= 2024.4.1.66479, >= 2025.1.0.66692 AND <= 2025.3.0.69570, >= 2026.1.0.70169 AND <= 2026.1.1.70276.
    Affected if Installed version falls within any of the listed affected ranges for Foxit PDF Editor
  4. Compare version against affected ranges for Foxit PDF Reader
    For Foxit PDF Reader, check if version <= 2026.1.1.36485 OR version <= 2026.1.1.70276. Note that both conditions indicate affected status.
    Affected if Installed version is either 2026.1.1.36485 or earlier, or 2026.1.1.70276 or earlier (both ranges indicate the version is affected)

The environment is affected if Foxit PDF Editor or Foxit PDF Reader is installed and the installed version falls within any of the specified affected version ranges for the respective product.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

From vendor data
Upgrade available Upgrade to a release after 2026.1.1.70276
Interim mitigation

Implement input validation to verify array bounds and element counts before reading from arrays during PRC file header parsing; add checks to ensure the underlying arrays contain expected elements before accessing them.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation8.0 h
  • Testing4.0 h
  • Review / QA2.0 h
17.0 hours of engineering $3,000
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,800.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57258 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-57258 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data