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-2025-26696 10 Mar 2025 See the vendor and CVE records for the affected range. 128.8 ≤ 128.*; 136 ≤ * Update reference ↗
CVE-2025-1015 4 Feb 2025 See the vendor and CVE records for the affected range. 128.7 ≤ 128.*; 135 ≤ * Update reference ↗
CVE-2025-0510 4 Feb 2025 See the vendor and CVE records for the affected range. 128.7 ≤ 128.*; 135 ≤ * Update reference ↗
CVE-2024-11159 13 Nov 2024 unspecified < 128.4.3; unspecified < 132.0.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-8394 6 Sep 2024 unspecified < 128.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2024-1936 4 Mar 2024 unspecified < 115.8.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50761 19 Dec 2023 unspecified < 115.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-50762 19 Dec 2023 unspecified < 115.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-3417 24 Jul 2023 unspecified < 115.0.1; unspecified < 102.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-25746 2 Jun 2023 unspecified < 102.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-1945 2 Jun 2023 unspecified < 102.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0616 2 Jun 2023 unspecified < 102.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0547 2 Jun 2023 unspecified < 102.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2023-0430 2 Jun 2023 unspecified < 102.7.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-43529 16 Feb 2023 unspecified < 91.3.0 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-45414 22 Dec 2022 unspecified < 102.5.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38478 22 Dec 2022 unspecified < 102.2; unspecified < 91.13; unspecified < 104 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38473 22 Dec 2022 unspecified < 102.2; unspecified < 91.13; unspecified < 104 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-38472 22 Dec 2022 unspecified < 102.2; unspecified < 91.13; unspecified < 104 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31747 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31742 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31741 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-31740 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31739 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31738 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31737 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-31736 22 Dec 2022 unspecified < 91.10; unspecified < 101 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3155 22 Dec 2022 unspecified < 102.3 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3034 22 Dec 2022 unspecified < 102.2.1; unspecified < 91.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-3033 22 Dec 2022 unspecified < 102.2.1; unspecified < 91.13.1 No fixed version is explicitly recorded in the structured CVE data. Update reference ↗
CVE-2022-3032 22 Dec 2022 unspecified < 102.2.1; unspecified < 91.13.1 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29917 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29916 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29914 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29913 22 Dec 2022 unspecified < 91.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29912 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29911 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-29909 22 Dec 2022 unspecified < 91.9; unspecified < 100 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28289 22 Dec 2022 unspecified < 91.8; unspecified < 99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28286 22 Dec 2022 unspecified < 91.8; unspecified < 99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28285 22 Dec 2022 unspecified < 91.8; unspecified < 99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28282 22 Dec 2022 unspecified < 91.8; unspecified < 99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-28281 22 Dec 2022 unspecified < 91.8; unspecified < 99 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-2226 22 Dec 2022 unspecified < 102; unspecified < 91.11 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1834 22 Dec 2022 unspecified < 91.10 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1520 22 Dec 2022 unspecified < 91.9 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1197 22 Dec 2022 unspecified < 91.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1196 22 Dec 2022 unspecified < 91.8 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2022-1097 22 Dec 2022 unspecified < 91.8; unspecified < 99 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-2022-0566 22 Dec 2022 unspecified < 91.6.1 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.