dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-5939

MEDIUM · 5.5 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 →
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
A crafted XFA PDF can trigger a use-after-free condition during calculate event processing, causing the application to crash and resulting in an arbitrary code execution.

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 · high confidence

A use-after-free vulnerability exists in PDF applications when processing crafted XFA (XML Forms Architecture) PDFs during calculate event processing. This memory corruption issue can be exploited to crash the application and achieve arbitrary code execution.

MitigationApply vendor patches for the affected PDF application, implement email/web gateway filtering for untrusted PDFs, and consider PDF sandboxing solutions until patches are deployed.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:N/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 Foxit PDF product installation
    Check for installed Foxit PDF Editor or Foxit PDF Reader by reviewing installed applications in Control Panel (Programs and Features), or search for foxit.exe or FoxitPDFReader.exe in common installation directories like C:\Program Files\Foxit Software\ or C:\Program Files (x86)\Foxit Software\
    Affected if Foxit PDF Editor or Foxit PDF Reader is installed on the system
  2. Determine installed Foxit version number
    Open Foxit application, then navigate to Help > About Foxit PDF Editor/Reader to display the exact version number, or right-click the Foxit executable in Program Files, select Properties, and view the Details tab for version info
    Affected if Version is Foxit PDF Editor 14.0.0 through 14.0.3, Foxit PDF Editor 2023.0.0 through 2026.1.0, or Foxit PDF Reader any version below 2026.1.1
  3. Verify XFA form processing is enabled
    In Foxit PDF application, go to File > Preferences > Forms and check if 'Enable XFA support' or similar XFA-related options are checked, or open a PDF and check document properties for XFA form presence
    Affected if XFA support is enabled and XFA-based PDF forms are being processed
  4. Assess exposure to untrusted PDFs
    Review typical workflow: check if the system regularly opens PDFs from external sources such as email attachments, web downloads, or file shares from users outside the organization
    Affected if Users routinely open PDF files from untrusted or external sources without prior sandboxing or content disarm

You are affected if Foxit PDF Editor (versions 14.0.0-14.0.3 or 2023.0.0-2026.1.0) or Foxit PDF Reader (version below 2026.1.1) is installed with XFA form processing enabled and users process untrusted PDF files.

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

Apply vendor patches for the affected PDF application, implement email/web gateway filtering for untrusted PDFs, and consider PDF sandboxing solutions until patches are deployed.

Recommended fix High confidence

Pdf Editor: upgrade to 14.0.4 or 2026.1.1; Pdf Reader: upgrade to 2026.1.1

  1. 1. Open the Foxit PDF application (Editor or Reader)
  2. 2. Navigate to Help > About Foxit PDF Editor (or About Foxit Reader) to confirm the current version
  3. 3. For Pdf Editor: If version is >= 14.0.0 and < 14.0.4, upgrade to 14.0.4; if version is >= 2023.0.0 and < 2026.1.1, upgrade to 2026.1.1
  4. 4. For Pdf Reader: If version is < 2026.1.1, upgrade to 2026.1.1
  5. 5. Visit the official Foxit download page at www.foxit.com to obtain the latest fixed version
  6. 6. Download the appropriate installer for your product and version
  7. 7. Run the installer and follow the prompts to complete the upgrade
  8. 8. Restart the application after installation completes
Caveat Standard upgrade; ensure compatibility with any existing PDF plugins or workflows

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

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing3.0 h
  • Review / QA1.0 h
10.0 hours of engineering $1,750
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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