dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-5941

HIGH · 7.1 CVSS v3.1 Published 2026-04-27
Fix available
A fix is available. Upgrade to 14.0.4 / 2026.1.1 or later.
See remediation →
74/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
Parsing logic flaws cause non-signature data to be misidentified as valid signatures when processing malformed form field hierarchies, leading to invalid memory writes and program crashes during internal data structure construction.

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

A parsing logic flaw in form field hierarchy processing causes non-signature data to be incorrectly identified as valid signatures. This misidentification triggers invalid memory writes during internal data structure construction, leading to potential program crashes.

MitigationImplement robust input validation and parsing logic to properly distinguish signature data from non-signature data in malformed form field hierarchies; ensure bounds checking and memory safety in data structure construction routines.

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:>= 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
High
Availability
High

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/I:H/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 PDF application
    Check program files for Foxit PDF Editor or Foxit PDF Reader installation directories, or use system inventory tools to list installed software
    Affected if Either Foxit PDF Editor or Foxit PDF Reader is present on the system
  2. Determine installed version number
    Open Foxit application, go to Help > About, or check the executable file properties for version information
    Affected if Version cannot be determined or is within affected ranges
  3. Compare version against affected ranges
    For Foxit PDF Editor: check if version is >= 14.0.0 and < 14.0.4, or >= 2023.0.0 and < 2026.1.1. For Foxit PDF Reader: check if version < 2026.1.1
    Affected if Installed version falls within any of the affected ranges listed
  4. Verify PDF form processing capability
    The vulnerability exploits form field hierarchy parsing; confirm the application has capability to open and process PDF forms with form fields
    Affected if Application can process PDF files with form fields and version is affected

User is affected if Foxit PDF Editor (versions 14.0.0 through 14.0.3, or 2023.0.0 through 2026.1.0) or Foxit PDF Reader (versions prior to 2026.1.1) is installed and processes PDF documents with form fields.

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 14.0.4 / 2026.1.1 or later
Fixed in 14.0.42026.1.1
Interim mitigation

Implement robust input validation and parsing logic to properly distinguish signature data from non-signature data in malformed form field hierarchies; ensure bounds checking and memory safety in data structure construction routines.

Recommended fix High confidence

Foxit PDF Editor 14.0.4 or later / Foxit PDF Editor 2026.1.1 or later / Foxit PDF Reader 2026.1.1 or later

  1. 1. Open Foxit PDF Editor or PDF Reader application
  2. 2. Navigate to the Help menu (or equivalent)
  3. 3. Select 'Check for Updates' or 'About Foxit PDF' to identify current version
  4. 4. Download the latest version from the official Foxit website (www.foxit.com) matching your product (PDF Editor or PDF Reader)
  5. 5. Run the installer and follow prompts to complete the upgrade
  6. 6. Restart the application after installation completes
  7. 7. Verify the version number reflects the fixed release (14.0.4 or later for 14.x branch; 2026.1.1 or later for 2023+ versions)

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation4.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
25.0 hours of engineering $4,400
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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