Pdf EditorApplication · Foxit

CVE-2026-3777

HIGH · 7.8 CVSS v3.1 Published 2026-04-01
Fix available
A fix is available. Upgrade to after 2025.3.0.69570 or later.
See remediation →
81/100
Remediation priority · High
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 properly validate the lifetime and validity of internal view cache pointers after JavaScript changes the document zoom and page state. When a script modifies the zoom property and then triggers a page change, the original view object may be destroyed while stale pointers are still kept and later dereferenced, which under crafted JavaScript and document structures can lead to a use-after-free condition and potentially allow 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 · moderate confidence

This is a use-after-free vulnerability in the application's view cache management. When JavaScript modifies the document zoom property and subsequently triggers a page change, the internal view object may be destroyed while the application retains stale pointers to it. Later dereferencing these dangling pointers can lead to arbitrary code execution.

MitigationImplement proper lifecycle management for view cache pointers, including explicit invalidation and validation checks before dereferencing, particularly when zoom or page state changes occur.

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

CVSS:3.1/AV:L/AC:L/PR:N/UI:R/S:U/C:H/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 Foxit product and version
    Open Foxit and go to Help > About Foxit PDF Editor/Reader. Note the exact version number displayed (for example, 13.2.2.24014 or 2025.3.0.35737).
    Affected if The installed version falls within any of the listed vulnerable ranges: Editor <= 13.2.2.24014; 14.0.0.33046 to 14.0.2.33402; 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; 13.2.2.63349; 14.0.0.68868 to 14.0.2.69164; 2023.1.0.55583 to 2023.3.0.6
  2. Verify JavaScript is enabled in the application
    In Foxit, go to File > Preferences > JavaScript. Confirm whether Enable JavaScript is checked.
    Affected if JavaScript is enabled, as the vulnerability requires JavaScript to modify the document zoom property and trigger the page change that leads to the use-after-free.
  3. Confirm PDF editing or viewing behavior
    Open any PDF document in Foxit. Use a JavaScript debugger or load a test PDF with JavaScript that modifies zoom (this.app zoom = X) followed by page navigation (this.pageNum = Y).
    Affected if The application exhibits crashes, abnormal behavior, or freezes when JavaScript zoom changes are followed by page transitions, which may indicate the use-after-free is being triggered.

A user is affected if they are running any Foxit PDF Editor or Reader version within the vulnerable ranges listed and have JavaScript enabled in the application settings.

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.

From vendor data
Upgrade available Upgrade to a release after 2025.3.0.69570
Interim mitigation

Implement proper lifecycle management for view cache pointers, including explicit invalidation and validation checks before dereferencing, particularly when zoom or page state changes occur.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation6.0 h
  • Implementation16.0 h
  • Testing8.0 h
  • Review / QA4.0 h
34.0 hours of engineering $6,000
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-3777 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

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-3777 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