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

Mozilla

Thunderbird

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-2020-6806 25 Mar 2020 unspecified < 68.6; unspecified < 74; unspecified < ESR68.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6807 25 Mar 2020 unspecified < 68.6; unspecified < 74; unspecified < ESR68.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6811 25 Mar 2020 unspecified < 68.6; unspecified < 74; unspecified < ESR68.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6812 25 Mar 2020 unspecified < 68.6; unspecified < 74; unspecified < ESR68.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6814 25 Mar 2020 unspecified < 68.6; unspecified < 74; unspecified < ESR68.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6800 2 Mar 2020 unspecified < 68.5; unspecified < 73; unspecified < ESR68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6798 2 Mar 2020 unspecified < 68.5; unspecified < 73; unspecified < ESR68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6797 2 Mar 2020 unspecified < 68.5; unspecified < 73; unspecified < ESR68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6795 2 Mar 2020 unspecified < 68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6794 2 Mar 2020 unspecified < 68.5 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-2020-6793 2 Mar 2020 unspecified < 68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6792 2 Mar 2020 unspecified < 68.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17012 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17011 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17010 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17009 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17008 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-17005 8 Jan 2020 before 68.3; before 71 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11745 8 Jan 2020 before 68.3; before 71 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-11739 27 Sep 2019 unspecified < 68.1; unspecified < 60.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11755 27 Sep 2019 unspecified < 68.1.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9800 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9815 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9816 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9817 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9818 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9819 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9820 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11691 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11692 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11693 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11694 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11698 23 Jul 2019 unspecified < 60.7; unspecified < 67 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11703 23 Jul 2019 unspecified < 60.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11704 23 Jul 2019 unspecified < 60.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11705 23 Jul 2019 unspecified < 60.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-11706 23 Jul 2019 unspecified < 60.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9801 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9796 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9795 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9794 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9793 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9792 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9791 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9790 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2019-9788 26 Apr 2019 unspecified < 60.6; unspecified < 66 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-18513 26 Apr 2019 unspecified < 60.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-18512 26 Apr 2019 unspecified < 60.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-18509 26 Apr 2019 unspecified < 60.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2018-18498 28 Feb 2019 unspecified < 60.4; unspecified < 64 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.