CVE-2026-8973: Memory safety bugs fixed in Thunderbird 151
Memory safety bugs present in Firefox 150. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
Other sources
Memory safety bugs present in Thunderbird 150. Some of these bugs showed evidence of memory corruption and we presume that with enough effort some of these could have been exploited to run arbitrary code.
— Mozilla
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 151 - Upgrade
Upgrade
Firefoxto a version that resolves this vulnerability.Fixed in 151 - Upgrade
Upgrade
Thunderbirdto a version that resolves this vulnerability.Fixed in 151
Event History
Peer vulnerabilities
Found alongside the following vulnerabilities.
- CVE-2026-8945
- CVE-2026-8946
- CVE-2026-8947
- CVE-2026-8948
- CVE-2026-8949
- CVE-2026-8950
- CVE-2026-8951
- CVE-2026-8952
- CVE-2026-8953
- CVE-2026-8954
- CVE-2026-8955
- CVE-2026-8956
- CVE-2026-8957
- CVE-2026-8958
- CVE-2026-8959
- CVE-2026-8960
- CVE-2026-8961
- CVE-2026-8962
- CVE-2026-8963
- CVE-2026-8964
- CVE-2026-8965
- CVE-2026-8966
- CVE-2026-8967
- CVE-2026-8968
- CVE-2026-8969
- CVE-2026-8970
- CVE-2026-8971
- CVE-2026-8972
- CVE-2026-8973
- CVE-2026-8974
- CVE-2026-8975
Frequently Asked Questions
What is the severity of CVE-2026-8973?
CVE-2026-8973 is classified as a critical vulnerability due to the potential for memory corruption leading to arbitrary code execution.
How do I fix CVE-2026-8973?
To fix CVE-2026-8973, update to Mozilla Firefox or Thunderbird version 151 or later.
What products are affected by CVE-2026-8973?
CVE-2026-8973 affects Mozilla Firefox versions earlier than 151 and Mozilla Thunderbird versions earlier than 151.
Can CVE-2026-8973 be exploited?
Yes, CVE-2026-8973 includes memory safety bugs that could potentially be exploited for arbitrary code execution.
Is there a workaround for CVE-2026-8973?
There is no specific workaround for CVE-2026-8973; the best mitigation is to update the affected software.