Evidence-linked product lifecycle intelligenceSUPPORT · SECURITY · RETIREMENT
← Search results
CVE-LINKED INVENTORY8 SECURITY RECORDS

Foxit Software Inc.

pdfonline.foxit.com

Affected and fixed version statements observed in the public BlackTree CVE catalogue. These statements describe vulnerability scope, not publisher support entitlement.

Lifecycle evidence status

This identity is present in BlackTree CVE records, but no product-specific publisher support or retirement history is currently registered in Lifecycle.

A missing support date does not mean the product is supported. CVE publication dates and affected-version ranges must not be interpreted as EOL dates.

CVE-observed version history

CVEPublishedAffected versionsFixed version informationPublisher evidence
CVE-2026-1592 3 Feb 2026 before 2026‑02‑03 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2026-1591 3 Feb 2026 before 2026‑02‑03 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66522 19 Dec 2025 before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66521 19 Dec 2025 before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66520 19 Dec 2025 before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66519 19 Dec 2025 pdfonline.foxit.com: before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66502 19 Dec 2025 pdfonline.foxit.com: before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2025-66501 19 Dec 2025 before 2025‑12‑01 No fixed version is explicitly recorded in the structured CVE data. Use CVE record

How this record is maintained

The CVE inventory is reconciled automatically from cve.blacktree.nl. Exact identity matches link to existing Lifecycle product or package histories. Unmatched products stay in a prioritised publisher-source research queue, and Lifecycle marks the date gap instead of inferring a support boundary from vulnerability data.