dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-57253

MEDIUM · 6.1 CVSS v3.1 Published 2026-07-08
Fix available
A fix is available. Upgrade to after 2026.1.1.36485 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
An abnormal image object causes the renderer to enter the wrong processing branch. When converting the scan lines, an invalid image buffer pointer is used, resulting in the application crashing.

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

This is a memory handling vulnerability in image rendering code where an abnormal or malformed image object causes the renderer to take an incorrect processing branch. During scan line conversion, an invalid (likely null or corrupted) image buffer pointer is dereferenced, causing the application to crash. This represents a denial-of-service vulnerability due to improper validation of image objects before pointer operations.

MitigationImplement rigorous validation of image objects and buffer pointers before scan line processing, ensuring proper error handling for abnormal image formats to prevent invalid pointer dereferences.

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
Pdf ReaderApplication
Affected:<= 2026.1.1.36485

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 for Foxit PDF Editor or Foxit PDF Reader installation by looking in Program Files for Foxit Software folder, or check Windows Add/Remove Programs, or right-click the executable and view Properties
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is installed
  2. Get installed version number
    In Foxit, go to Help > About Foxit PDF (Editor/Reader). The version is displayed as a four-part number (e.g., 13.2.4.24048 or 2026.1.1.36485)
    Affected if Version cannot be determined or is not visible
  3. Compare Editor version against affected ranges
    If using Foxit PDF Editor, compare your version number to these ranges: <=13.2.4.24048; 14.0.0.33046 to 14.0.4.33508; 2023.1.0.15510 to 2023.3.0.23028; 2024.1.0.23997 to 2024.4.1.27687; 2025.1.0.27937 to 2025.3.0.35737; 2026.1.0.36452 to 2026.1.1.36485
    Affected if Version falls within any of these ranges
  4. Compare Reader version against affected range
    If using Foxit PDF Reader, compare your version number to <=2026.1.1.36485
    Affected if Version is 2026.1.1.36485 or lower

You are affected if Foxit PDF Editor or Reader is installed and the version falls within the specified vulnerable ranges.

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.

dbcve · scoped
Upgrade available Upgrade to a release after 2026.1.1.36485
Interim mitigation

Implement rigorous validation of image objects and buffer pointers before scan line processing, ensuring proper error handling for abnormal image formats to prevent invalid pointer dereferences.

Recommended fix Moderate confidence

Pdf Editor: latest version (14.x or 2025+); Pdf Reader: 2026.1.2 or later

  1. 1. Identify the currently installed Foxit Pdf Editor or Pdf Reader version from the application (Help > About)
  2. 2. For Pdf Editor: If version is 13.2.x, upgrade to 13.2.5 or later (or migrate to a newer version line)
  3. 3. For Pdf Editor: If version is 14.0.x, upgrade to 14.0.5 or later
  4. 4. For Pdf Editor: If version is 2023.x, upgrade to 2023.4 or later
  5. 5. For Pdf Editor: If version is 2024.x, upgrade to 2025 or later (version 2024.5 or newer if available)
  6. 6. For Pdf Reader: Upgrade to version 2026.1.2 or later
  7. 7. Download updates only from the official Foxit website (www.foxit.com) or trusted enterprise distribution channels
  8. 8. Restart the application after upgrade and verify functionality with test PDF documents
Caveat Newer major versions may include UI changes; enterprise deployments should test compatibility with existing workflows

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing8.0 h
  • Review / QA4.0 h
30.0 hours of engineering $5,280
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-57253 — 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-57253 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