CVE-2026-8092: Memory safety bugs fixed in Firefox ESR 115.35.2, Firefox ESR 140.10.2 and Firefox 150.0.2
Memory safety bugs present in Firefox ESR 115.35.1, Firefox ESR 140.10.1 and Firefox 150.0.1. 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. This vulnerability was fixed in Firefox 150.0.2, Firefox ESR 140.10.2, Firefox ESR 115.35.2, Thunderbird 150.0.2, and Thunderbird 140.10.2.
Security readout for executives and security teams
Plain-English summary
Mozilla fixed multiple memory-safety defects that could corrupt memory and, with sufficient effort, potentially allow arbitrary code execution. Firefox 150.0.1, ESR 140.10.1, and ESR 115.35.1 are explicitly vulnerable. Thunderbird is also affected, but the bundle does not identify its complete vulnerable version range.
Executive priority
Treat this as a high-priority endpoint patching issue. Expedite updates across browser and email-client fleets, especially privileged or widely used systems. No active exploitation is established, so emergency incident assumptions are unwarranted; however, the potential for remote arbitrary code execution and broad client exposure supports rapid remediation and completion tracking.
Technical view
The grouped flaws include out-of-bounds reads, use-after-free, and out-of-bounds writes. CVSS 3.1 rates them 8.1: remotely reachable, high complexity, no privileges or user interaction, with potentially high confidentiality, integrity, and availability impact. Mozilla reports evidence of memory corruption but describes code execution as presumed rather than demonstrated.
Likely exposure
Exposure is highest where the identified Firefox releases remain installed on workstations, servers, kiosks, or managed endpoints. Thunderbird deployments below the named fixed releases require vendor-guidance review because the supplied evidence does not define their exact vulnerable range. Red Hat-packaged installations should be assessed against the applicable Red Hat errata.
Exploitation context
The bundle provides no evidence of active exploitation, and CVE-2026-8092 is not marked as CISA KEV. Mozilla states some defects showed memory corruption and might permit arbitrary code execution with enough effort. Exploitation is rated high complexity, but potentially severe consequences justify prompt remediation.
Researcher notes
This CVE aggregates multiple memory-safety bugs under CWE-125, CWE-416, and CWE-787. The bundle does not establish which individual defect is most exploitable, provide proof of code execution, or define Thunderbird's complete affected range. Fixed-version statements are strong; broader affected-version conclusions should be validated against Mozilla advisories and distribution-specific package metadata.
Mitigation direction
Update Firefox to 150.0.2, ESR 140.10.2, ESR 115.35.2, or a later supported release.
Update Thunderbird to 150.0.2, 140.10.2, or a later supported release.
Apply applicable Red Hat security errata to vendor-packaged installations.
Prioritize internet-facing, privileged, and broadly deployed browser or mail-client endpoints.
Consult Mozilla guidance where unsupported versions or deployment constraints prevent immediate updating.
Validation and detection
Inventory installed Firefox and Thunderbird versions across managed and unmanaged endpoints.
Flag Firefox 150.0.1, ESR 140.10.1, and ESR 115.35.1 as explicitly vulnerable.
Confirm Thunderbird meets or exceeds the applicable named fixed release.
Verify Red Hat package versions against the relevant RHSA advisory.
Re-scan endpoints after deployment and investigate systems that remain below fixed versions.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-125: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
The CVE wording references code or command execution, so execution technique review may help defensive triage. This is a Glexia inferred lookup path, not an official MITRE, ATT&CK, or CVE Program mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
2CVSS vectors
5Timeline events
2ADP providers
31Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
2 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-125 · source CWE mapping
Out-of-bounds Read
Out-of-bounds Read represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Use After Free represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.
Out-of-bounds Write represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.