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

Mozilla

Firefox

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 CVE identity is linked to the Lifecycle record Firefox. Use that record for publisher support phases and retirement dates.

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-23975 26 Feb 2021 < 86 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2021-23976 26 Feb 2021 < 86 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26971 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26972 7 Jan 2021 unspecified < 84 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26973 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26974 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26975 7 Jan 2021 unspecified < 84 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26976 7 Jan 2021 unspecified < 84 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26977 7 Jan 2021 unspecified < 84 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26978 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26979 7 Jan 2021 unspecified < 84 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-35111 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-35112 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-35113 7 Jan 2021 unspecified < 84; unspecified < 78.6 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-35114 7 Jan 2021 unspecified < 84 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-26969 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26968 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26967 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26966 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26965 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26964 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26963 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26962 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26961 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26960 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26959 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26958 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26957 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26956 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26955 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26954 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26953 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26952 9 Dec 2020 < 83 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26951 9 Dec 2020 < 83; < 78.5 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-26950 9 Dec 2020 < 82.0.3; < 78.4.1; < 78.4.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-6829 28 Oct 2020 unspecified < 80 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, applications using NSS or NSPR (for example, Firefox) must be restarted for this update to take effect. Update reference ↗
CVE-2020-15680 22 Oct 2020 unspecified < 82 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15681 22 Oct 2020 unspecified < 82 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15682 22 Oct 2020 unspecified < 82 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15684 22 Oct 2020 unspecified < 82 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-12401 8 Oct 2020 unspecified < 80 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, applications using NSS or NSPR (for example, Firefox) must be restarted for this update to take effect. Update reference ↗
CVE-2020-12400 8 Oct 2020 unspecified < 80 For details on how to apply this update, which includes the changes described in this advisory, refer to: https://access.redhat.com/articles/11258 After installing this update, applications using NSS or NSPR (for example, Firefox) must be restarted for this update to take effect. Update reference ↗
CVE-2020-15663 1 Oct 2020 unspecified < 80; unspecified < 78.2; unspecified < 68.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15664 1 Oct 2020 unspecified < 80; unspecified < 78.2; unspecified < 68.12 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15665 1 Oct 2020 unspecified < 80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15666 1 Oct 2020 unspecified < 80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15667 1 Oct 2020 unspecified < 80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15668 1 Oct 2020 unspecified < 80 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15670 1 Oct 2020 unspecified < 80; unspecified < 78.2 No fixed version is explicitly recorded in the structured CVE data. Use CVE record
CVE-2020-15673 1 Oct 2020 unspecified < 81; unspecified < 78.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.