dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-5937

MEDIUM · 5.5 CVSS v3.1 Developing Published 2026-04-27
Fix available
A fix is available. Upgrade to 13.2.4 / 14.0.4 or later.
See remediation →
58/100
Remediation priority · Elevated
No privileges

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
Insufficient parameter verification leads to the occurrence of format errors in files, which will trigger an unhandled "std::invalid_argument" exception, ultimately causing the program to terminate.

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 · low confidence
Developing — this CVE was published recently and its authoritative NVD entry is still being established, so we're holding a technical summary until the source data settles rather than publish something unreliable. Re-checking after 2026-07-31.

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>= 14.0.0, < 14.0.4>= 2023.0.0, < 2026.1.1
Pdf ReaderApplication
Affected:< 2026.1.1

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
None
Integrity
None
Availability
High

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

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 13.2.4 / 14.0.4 / 2026.1.1 or later
Fixed in 13.2.414.0.42026.1.1
Recommended fix High confidence

Foxit Pdf Editor 13.2.4 (or 14.0.4 or 2026.1.1 depending on major version line); Foxit Pdf Reader 2026.1.1

  1. 1. Identify the currently installed Foxit PDF Editor or PDF Reader version by opening the application and checking Help > About.
  2. 2. If running Pdf Editor version < 13.2.4: upgrade to version 13.2.4 or later.
  3. 3. If running Pdf Editor version 14.0.0-14.0.3: upgrade to version 14.0.4 or later.
  4. 4. If running Pdf Editor version 2023.0.0-2026.1.0: upgrade to version 2026.1.1 or later.
  5. 5. If running Pdf Reader version < 2026.1.1: upgrade to version 2026.1.1 or later.
  6. 6. Download the appropriate fixed version from the official Foxit website at www.foxit.com.
  7. 7. Uninstall the current version and install the upgraded version, or run the installer to upgrade in place.
  8. 8. Verify the application launches without errors and test with previously problematic PDF files if available.
Caveat Minor: Users on very old version lines may notice UI changes when upgrading across major version jumps (e.g., from v13 to v14 or v2023 to v2026)

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

We can perform the upgrade in your staging environment and verify nothing breaks — typical engagement from $1,600. Get the upgrade done

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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