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

Foxit

Reader

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

Lifecycle evidence status

Official registry publication history is available at reader, but registry activity is not a publisher support boundary.

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-2021-34831 4 Aug 2021 10.1.4.37651 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31473 21 May 2021 10.1.3.37598 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31472 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31471 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31470 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31469 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31468 7 May 2021 10.1.3.37598 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31467 7 May 2021 10.1.3.37598 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31466 7 May 2021 10.1.3.37598 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31465 7 May 2021 10.1.3.37598 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31464 7 May 2021 10.1.3.37598 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31463 7 May 2021 10.1.3.37598 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31462 7 May 2021 10.1.3.37598 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31461 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31460 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31459 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31458 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31457 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31456 7 May 2021 10.1.1.37576 An authoritative update reference is available, but the fixed version is not recorded in the structured CVE fields. Check the linked vendor advisory for the applicable release. Update reference ↗
CVE-2021-31455 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31454 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31453 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31452 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31451 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31450 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31449 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31448 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31447 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31446 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31445 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31444 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31443 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31442 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-31441 7 May 2021 10.1.1.37576 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-27860 11 Feb 2021 10.0.1.35811 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-17417 13 Oct 2020 10.0.1.35811 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-17416 13 Oct 2020 10.0.0.35798 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-17414 13 Oct 2020 10.0.0.35798 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-10907 22 Apr 2020 9.7.1.29511 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-10906 22 Apr 2020 9.7.1.29511 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-10900 22 Apr 2020 9.7.1.29511 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-10899 22 Apr 2020 9.7.1.29511 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8857 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8852 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8851 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8850 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8849 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8848 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8847 13 Feb 2020 9.7.0.29455 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-8844 13 Feb 2020 9.6.0.25114 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.