CVE-2026-57259
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 · uneditedThe input file does not need to be strictly in a structurally valid PDF format. Instead, after reviewing the content, the original document disguised as a PDF will be sent to the parser. Malicious documents will construct malicious external entities that, through the protocol, point to local paths, thereby allowing access to any local files within the user's permission range.
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 confidenceThis is an XML External Entity (XXE) injection vulnerability in a PDF parser. The parser accepts documents disguised as PDFs that contain malicious XML content with external entity references pointing to local file paths via the file:// protocol, allowing unauthorized read access to local files within the user's permission scope.
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<= 2026.1.1.36485CVSS 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
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- Required
- Scope
- Unchanged
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N
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 installed Foxit product and versionOpen the Foxit application, go to Help > About, or right-click the executable (FoxitPDFEditor.exe or FoxitPDFReader.exe) and select Properties to view the Version information. On Windows, you can also check Add/Remove Programs or the registry under HKLM\SOFTWARE\Foxit Software for the installed version.Affected if The displayed version falls within any of the affected ranges: <= 13.2.4.24048; >= 14.0.0.33046 and <= 14.0.4.33508; >= 2023.1.0.15510 and <= 2023.3.0.23028; >= 2024.1.0.23997 and <= 2024.4.1.27687; >= 2025.1.0.27937 and <= 2025.3.0.35737; >= 2026.1.0.36452 and <= 2026.1.1.36485 for Editor, or <= 20
-
Confirm PDF processing handles embedded XML contentCreate a test PDF containing an XML declaration and external entity reference (for example, a PDF with embedded XML metadata or content streams that include DOCTYPE declarations with entity definitions), then attempt to open and process it in the Foxit application to see if the parser interprets the XML entities.Affected if The application parses and resolves the external entity references within the document, indicating XXE processing is active.
-
Check for XML external entity configuration settingsExamine Foxit preferences or configuration files for options related to XML parsing, DTD processing, or external entity handling. On Windows, check the user preferences file in %APPDATA%\Foxit Software\Foxit PDF Editor\settings or similar paths for keywords like 'XML', 'XXE', 'ExternalEntity', or 'DTD'.Affected if No option exists to disable external entity processing, or the setting allows DTD/external entity resolution.
A user is affected if they have Foxit Pdf Editor or Reader installed with a version matching the affected ranges AND the application processes PDF documents containing embedded XML with external entity references.
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 dataDisable XML external entity processing in the parser configuration, implement strict PDF structure validation before XML parsing, and sanitize or reject documents containing XML declarations.
- Consultation4.0 h
- Implementation12.0 h
- Testing8.0 h
- Review / QA4.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,808.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-57259 — 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-57259 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