CVE-2026-57257
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 · uneditedDuring the PRC parsing stage, there is a lack of boundary verification for the PRC entity index, which leads to an out-of-bounds read of the entity array. As a result, the 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 confidenceThe vulnerability is an out-of-bounds read in the PRC (likely a proprietary or common 3D/file format) parser caused by missing boundary validation on the entity index when accessing an entity array. This allows reading beyond array bounds, leading to application crash.
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<= 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.68868, <= 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<= 2026.1.1.36485<= 2026.1.1.70276CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Identify Foxit product typeOpen Foxit and go to Help > About to determine if you are using Foxit PDF Reader or Foxit PDF EditorAffected if The product is Foxit PDF Reader or Foxit PDF Editor
-
Determine installed version numberIn the About dialog, locate the exact version number (for example: 13.2.4.24048 or 2024.1.0.23997)Affected if A specific version number is displayed
-
Compare against affected version rangesMatch your installed version against all listed vulnerable ranges: Editor <= 13.2.4.24048; Editor >= 14.0.0.33046 <= 14.0.4.33508; Editor >= 2023.1.0.15510 <= 2023.3.0.23028; Editor >= 2024.1.0.23997 <= 2024.4.1.27687; Editor >= 2025.1.0.27937 <= 2025.3.0.35737; Editor >= 2026.1.0.36452 <= 2026.1.1.36485; Editor <= 13.2.3.63444; Editor >= 14.0.0.68868 <= 14.0.3.69295; Editor >= 2023.1.0.55583 <= 2023.3.0.63083; Editor >= 2024.1.0.63682 <= 2024.4.1.66479; Editor >= 2025.1.0.66692 <= 2025.3.0.69570; Editor >= 2026.1.0.70169 <= 2026.1.1.70276; Reader <= 2026.1.1.36485; Reader <= 2026.1.1.70276Affected if Your installed version falls within any of these ranges
-
Verify PRC file handling capabilityCheck if the Foxit application has PRC import or conversion functionality enabled, as the vulnerability triggers when parsing PRC filesAffected if PRC file handling features are available and the product version is vulnerable
You are affected if you have Foxit PDF Reader or Editor installed with a version number matching any of the vulnerable ranges and you handle PRC files.
Generated from the published advisory. Verify against your own configuration.
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 dataAdd proper bounds checking before array access in the PRC entity parsing code to validate the entity index against the array bounds before dereferencing.
- Consultation2.0 h
- Implementation4.0 h
- Testing4.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,328.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57257 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-57257 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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