Evidence used
- No CISA KEV confirmation is currently recorded.
- EPSS is 0.64% for the current model date.
BlackTreeCVE IntelligenceMozilla · Firefox
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Debian, ubuntu findings are scoped to the named distribution, release and source package. An absent finding does not mean a package is unaffected.
A published vendor fix does not prove that a matching update is enabled and installable on a particular asset. Confirm the local package candidate before scheduling remediation.
| Distribution release | Source package | Vendor state | Fixed version | Evidence |
|---|---|---|---|---|
| Debian trixietrixie · source | firefox-esr | Vendor fix publishedDebian records a fixed source-package version for this release. | 140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.15.0-2.1+deb13u1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian trixietrixie · source | thunderbird | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | firefox-esr | Vendor fix publishedDebian records a fixed source-package version for this release. | 140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.12.0-1+deb12u5 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian bookwormbookworm · source | thunderbird | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | firefox-esr | Vendor fix publishedDebian records a fixed source-package version for this release. | 140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.16.0-3 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian forkyforky · source | thunderbird | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | firefox | Vendor fix publishedDebian records a fixed source-package version for this release. | 147.0.4-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | firefox-esr | Vendor fix publishedDebian records a fixed source-package version for this release. | 140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | libvpx | Vendor fix publishedDebian records a fixed source-package version for this release. | 1.16.0-3 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Debian sidsid · source | thunderbird | Vendor fix publishedDebian records a fixed source-package version for this release. | 1:140.8.0esr-1 | Debian Security Tracker ↗Source updated 5 Oct 2026 |
| Ubuntu 24.04 LTSnoble · standard archive | libvpx | Vendor fix publishedCanonical reports that a fixed source package version has been published. Repository candidate availability is not checked by BlackTree. | 1.14.0-1ubuntu2.3 | Canonical Ubuntu Security ↗Source updated 5 Oct 2026 |
High technical severity; prioritise exposed affected systems while verifying vendor guidance.
Patch availableHeap buffer overflow in libvpx. This vulnerability was fixed in Firefox 147.0.4, Firefox ESR 140.7.1, Firefox ESR 115.32.1, Thunderbird 140.7.2, and Thunderbird 147.0.2.
Heap buffer overflow in libvpx. This vulnerability was fixed in Firefox 147.0.4, Firefox ESR 140.7.1, Firefox ESR 115.32.1, Thunderbird 140.7.2, and Thunderbird 147.0.2.
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
Heap buffer overflow in libvpx. This vulnerability was fixed in Firefox 147.0.4, Firefox ESR 140.7.1, Firefox ESR 115.32.1, Thunderbird 140.7.2, and Thunderbird 147.0.2.
A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
An attacker operating through a network path may attempt exploitation without authentication after a user interaction. If successful, the issue may cause the confidentiality, integrity or availability impact described by the vendor.
CVSS severity, EPSS forecast probability, public exploit material and CISA-confirmed exploitation are separate signals.
No CISA KEV match was present at the last successful refresh. This means no confirmation from that source, not proof of no exploitation.
No exploit-tagged reference or CISA SSVC proof-of-concept state is currently recorded. Research may still exist outside the structured feeds.
CWE-122: Heap-based Buffer Overflow. A heap overflow condition is a buffer overflow, where the buffer that can be overwritten is allocated in the heap portion of memory, generally meaning that the buffer was allocated using a routine such as malloc().
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:HCommon Vulnerability Scoring System 3.1: the compact vector below is decoded into plain language.
Operational remediation based on structured source evidence.
Published 16 Feb 2026 · Last source change 15 Jul 2026, 02:49 UTC · CWE-122 · Heap-based Buffer Overflow
Missing structured fields: affected versions. Missing data is not evidence of low risk; review the primary advisory.
No material field changes have been recorded since change tracking began. Routine source refreshes and cosmetic edits are intentionally excluded.