dbcve.org
Pdf EditorApplication · Foxit

CVE-2025-66499

HIGH · 7.8 CVSS v3.1 Published 2025-12-19
Fix available
A fix is available. Upgrade to after 2025.2.1.69005 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
A heap-based buffer overflow vulnerability exists in the PDF parsing of Foxit PDF Reader when processing specially crafted JBIG2 data. An integer overflow in the calculation of the image buffer size may occur, potentially allowing a remote attacker to execute arbitrary code.

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

Foxit PDF Reader contains a heap-based buffer overflow vulnerability in its PDF parsing engine when processing JBIG2 image data embedded in PDFs. The vulnerability stems from an integer overflow when calculating the required image buffer size, which can result in allocating a smaller-than-needed buffer and subsequently writing beyond its bounds, potentially enabling arbitrary code execution.

MitigationApply vendor-supplied patches from Foxit when available. Until patched, avoid opening PDF files from untrusted sources and consider disabling JBIG2 rendering in reader settings if the option exists.

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.1.23955>= 14.0.0.33046, <= 14.0.1.33197>= 2023.1.0.15510, <= 2023.3.0.23028>= 2024.1.0.23997, <= 2024.4.1.27687>= 2025.1.0.27937, <= 2025.2.1.33197<= 13.2.1.63315>= 14.0.0.33046, <= 14.0.1.69005>= 2023.1.0.15510, <= 2023.3.0.63083>= 2024.1.0.23997, <= 2024.4.1.66479>= 2025.1.0.27937, <= 2025.2.1.69005
Pdf ReaderApplication
Affected:<= 2025.2.1.33197<= 2025.2.1.69005

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. Confirm Foxit PDF product is installed
    Locate Foxit PDF Reader or Foxit PDF Editor installation directory, typically under Program Files or Program Files (x86). Check for FoxitPDFReader.exe or FoxitPDFEditor.exe files.
    Affected if Either Foxit PDF Reader or Foxit PDF Editor executable is found on the system.
  2. Retrieve installed product version
    Right-click the Foxit executable, select Properties, and view the Details tab for the Product Version field. Alternatively, run the executable with a version flag or check Add/Remove Programs for the installed version.
    Affected if A version number is obtained that can be compared against affected ranges.
  3. Compare version against affected ranges
    Match your installed version number against the following affected ranges: versions <= 13.2.1.23955; versions >= 14.0.0.33046 through <= 14.0.1.33197; versions >= 2023.1.0.15510 through <= 2023.3.0.23028; versions >= 2024.1.0.23997 through <= 2024.4.1.27687; versions >= 2025.1.0.27937 through <= 2025.2.1.33197; or versions <= 13.2.1.63315; versions >= 14.0.0.33046 through <= 14.0.1.69005; versions >= 2023.1.0.15510 through <= 2023.3.0.63083; versions >= 2024.1.0.23997 through <= 2024.4.1.66479; versions >= 2025.1.0.27937 through <= 2025.2.1.69005; or versions <= 2025.2.1.33197 or <= 2025.2.1.6
    Affected if The installed version falls within any of the listed affected version ranges.
  4. Determine if JBIG2 image rendering is active
    Open Foxit Reader/Editor preferences or settings panel. Look for image rendering, PDF conversion, or security settings related to JBIG2 image decoding. Check if the feature is enabled or set to automatic processing.
    Affected if JBIG2 image rendering or decoding is enabled, meaning PDFs containing JBIG2 data will trigger the vulnerable parsing code path.
  5. Assess exposure to untrusted PDFs
    Review recent PDF files opened with the Foxit product. Determine if documents from external or untrusted sources have been processed, as the vulnerability is triggered by specially crafted PDF files with embedded JBIG2 image data.
    Affected if The product has been used to open PDF files from untrusted or unknown sources, which could contain malicious JBIG2 payload.

If Foxit PDF Reader or Editor is installed with a version matching any of the affected ranges and JBIG2 image rendering is enabled, the environment is vulnerable to CVE-2025-66499 when processing crafted 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.

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

Apply vendor-supplied patches from Foxit when available. Until patched, avoid opening PDF files from untrusted sources and consider disabling JBIG2 rendering in reader settings if the option exists.

Fix this in Pdf Editor Scoped from the published advisory
  • Consultation3.0 h
  • Implementation6.0 h
  • Testing5.0 h
  • Review / QA3.0 h
17.0 hours of engineering $2,970
Get the upgrade done

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

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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