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

Document Foundation

LibreOffice

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 libreoffice, 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-2019-9853 27 Sep 2019 6.2 series < 6.2.7; 6.3 series < 6.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9855 6 Sep 2019 6.2 < 6.2.7; 6.3 < 6.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9854 6 Sep 2019 6.2 < 6.2.7; 6.3 < 6.3.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9852 15 Aug 2019 unspecified < 6.2.6 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-2019-9851 15 Aug 2019 unspecified < 6.2.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9850 15 Aug 2019 unspecified < 6.2.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9849 17 Jul 2019 unspecified < 6.2.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9848 17 Jul 2019 unspecified < 6.2.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9847 9 May 2019 unspecified < 6.1.6; unspecified < 6.2.3 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.