dbcve.org
Pdf EditorApplication · Foxit

CVE-2026-3778

MEDIUM · 5.5 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 2025.3.0.69570 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
The application does not detect or guard against cyclic PDF object references while handling JavaScript in PDF. When pages and annotations are crafted that reference each other in a loop, passing the document to APIs (e.g., SOAP) that perform deep traversal can cause uncontrolled recursion, stack exhaustion, and application crashes.

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 denial-of-service vulnerability exists in PDF object traversal where cyclic references between PDF pages and annotations cause unbounded recursion. When documents with mutually referencing objects are processed through deep traversal APIs (like SOAP), the application experiences stack exhaustion and crashes.

MitigationImplement cycle detection using a visited-object tracking set and enforce recursion depth limits in PDF traversal APIs, or refactor recursive traversal to use iterative approaches with explicit stack management.

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.2.24014>= 14.0.0.33046, <= 14.0.2.33402>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.3.0.35737<= 13.2.2.63349>= 14.0.0.68868, <= 14.0.2.69164>= 2023.1.0.55583, <= 2023.3.0.63083>= 2024.1.0.63682, <= 2024.4.1.66479>= 2025.1.0.66692, <= 2025.3.0.69570
Pdf ReaderApplication
Affected:<= 2025.3.0.35737<= 2025.3.0.69570

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 installed Foxit PDF product
    Open the application, then go to Help > About Foxit PDF Editor (or Reader) to view the exact version number. Alternatively, locate the executable file in Program Files and check its properties.
    Affected if The installed application is Foxit Pdf Editor or Foxit Pdf Reader
  2. Compare version against affected ranges
    Match your installed version number to the affected version list: Editor <= 13.2.2.24014; >= 14.0.0.33046 <= 14.0.2.33402; >= 2023.1.0.15510 <= 2023.3.0.23028; >= 2024.1.0.23997 <= 2024.4.1.27687; >= 2025.1.0.27937 <= 2025.3.0.35737; <= 13.2.2.63349; >= 14.0.0.68868 <= 14.0.2.69164; >= 2023.1.0.55583 <= 2023.3.0.63083; >= 2024.1.0.63682 <= 2024.4.1.66479; >= 2025.1.0.66692 <= 2025.3.0.69570. Reader <= 2025.3.0.35737 or <= 2025.3.0.69570.
    Affected if Your installed version falls within any of the listed affected ranges
  3. Check for programmatic PDF processing
    Review any scripts, applications, or automation that invoke Foxit PDF products through SOAP, deep traversal APIs, or command-line operations that process untrusted PDF documents.
    Affected if Your environment uses Foxit to process PDF documents through traversal APIs or SOAP interfaces with documents that may contain cyclic object references

You are affected if you have Foxit PDF Editor or Reader installed with a version matching the affected ranges AND you process PDF documents containing cyclic references through deep traversal or SOAP APIs.

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 2025.3.0.69570
Interim mitigation

Implement cycle detection using a visited-object tracking set and enforce recursion depth limits in PDF traversal APIs, or refactor recursive traversal to use iterative approaches with explicit stack management.

Recommended fix Moderate confidence

For Pdf Editor: upgrade to version > 2024.4.1.27687 (latest 2024.x or 2025.x release); For Pdf Reader: upgrade to version > 2025.3.0.69570 (latest release)

  1. 1. Identify the exact Foxit product installed (Pdf Editor or Pdf Reader) and current version number
  2. 2. Navigate to the official Foxit website (www.foxit.com) and locate the downloads or support section
  3. 3. Download the latest version of the installed product
  4. 4. Uninstall the current version of Foxit Pdf Editor or Pdf Reader
  5. 5. Install the latest downloaded version
Caveat Review release notes for any feature changes or migration requirements between major version jumps

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

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

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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