Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryServe crafted networking content
-
ExploitWin race condition in Networking
-
ExecutionEscape content sandbox
-
ImpactExecute code on host
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to load attacker-controlled web content in Firefox (UI:R - no victim action, no exploitation), and then requires the attacker to win a timing-dependent race condition in the Networking component, which high attack complexity (AC:H) indicates is not reliably achievable per attempt. No authentication is required (PR:N, unauthenticated). The principal limiting factors are the mandatory user interaction, the probabilistic nature of the race window, and the need for the user to be running an unpatched version prior to Firefox 158 / ESR 153.5; there is no special non-default configuration called out in the description. |
| Impact | This is a high-severity (CVSS 8.3) sandbox escape in Firefox's Networking component triggered by a race condition (CWE-362). The CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H is internally consistent with a browser-rendered attack: network delivery (AV:N), no authentication (PR:N), required user interaction (UI:R, i.e. the victim loads attacker content), and a scope change (S:C) reflecting the break out of the content sandbox into the host, yielding full confidentiality, integrity, and availability impact. The high attack complexity (AC:H) is the dominant mitigating signal and is well-grounded: winning a race condition reliably is timing-dependent and not guaranteed per attempt. Exploitation signals are LOW and mutually reinforcing: EPSS is only 0.16% (5th percentile), there is no CISA KEV listing, and no public exploit identified at time of analysis - so there is no evidence of active exploitation or available weaponization. The tension here is severity vs. likelihood: raw impact is critical-adjacent, but the real-world probability signals (low EPSS, no KEV, no POC, AC:H) argue this is a serious-but-not-emergency patch priority rather than an actively exploited crisis. Prioritize patching because the affected product is a ubiquitous browser and sandbox escapes are high-value, but there is no indication this warrants out-of-band emergency response based on current data. |
| Exploit ScenarioDerived | An attacker hosts or injects malicious web content and lures a victim into loading it in Firefox; the content drives the vulnerable Networking code path to win a timing-dependent race condition, corrupting state and escaping the content sandbox to run code with the host browser process's privileges. Because attack complexity is high, exploitation is not reliable on a single attempt and may require repeated triggering. No public exploit code has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Sandbox escape in Mozilla Firefox allows attacker-controlled web content to break out of the browser's content sandbox by winning a timing-dependent race condition in the Networking component (CWE-362), rated CVSS 8.3 with scope change (S:C), meaning compromise extends beyond the sandboxed process. Exploitation is unauthenticated (PR:N) and remote (AV:N) but requires the victim to load attacker-controlled web content (UI:R) and is unreliable per attempt due to high attack complexity (AC:H). No public exploit code or confirmed active exploitation was identified at time of analysis, and EPSS is low at 0.16% (5th percentile); the vulnerability is fixed in Firefox 158 and Firefox ESR 153.5.
RemediationAI
Vendor-released patch: upgrade to Mozilla Firefox 158 (rapid-release channel) or Mozilla Firefox ESR 153.5 (Extended Support Release channel); these are the exact fixed versions documented in the Mozilla advisories MFSA2026-106, MFSA2026-108, MFSA2026-109, and MFSA2026-110 (see https://www.mozilla.org/security/advisories/mfsa2026-106/ and https://bugzilla.mozilla.org/show_bug.cgi?id=2069910). Enterprise and managed fleets should enforce the ESR 153.5 floor via Firefox policy configuration (AppUpdate / ExtensionSettings-style auto-update enforcement) and verify build numbers through about:support, since the ESR channel is often pinned and can lag behind rapid release. No vendor-documented workaround beyond patching is identified in the available data; because exploitation requires the victim to load attacker-controlled web content and to win a race window, interim compensating controls with their trade-offs are: restrict untrusted browsing in high-value environments (reduces exposure but blocks legitimate sites and is difficult to sustain), and harden via DNS/network filtering of untrusted content (lower efficacy against compromised or typo-squatted legitimate domains, and imposes latency or breakage). Disabling JavaScript wholesale would blunt web-delivered triggers but breaks most modern sites and is not validated by vendor guidance for this specific defect. Given EPSS 0.16% (5th percentile) and no public exploit code or KEV listing at time of analysis, patching on a standard high-severity cadence is appropriate, with accelerated remediation for users who routinely browse untrusted content in the same profile as sensitive sessions.
Affects your stack
Find out whether the stacks and servers you run are on an affected version.
Checking this CVE against your own stacks and servers is part of the Basic plan and up.
Technical ContextAI · show details
The flaw is a race condition (CWE-362) in Firefox's Networking component (the Necko stack handling HTTP, sockets, and content-process networking requests). Race conditions of this class arise when two or more execution paths - here, likely an asynchronous networking callback and a privilege or resource check in the browser's inter-process sandboxing model - act on shared state without adequate synchronization, producing a narrow window in which state can be changed after validation but before use (a TOCTOU-style defect). Because this is a sandbox escape rather than a plain memory-safety bug, the CVSS vector CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H is notable: Scope is Changed (S:C), reflecting that impact moves from the unprivileged content process into the browser's higher-privilege process space, with High confidentiality, integrity, and availability impact should the escape succeed. AC:H captures the probabilistic nature of the race - exploitation is not reliably achievable on each attempt, and UI:R reflects that the victim must render attacker-controlled web content. The CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* covers Firefox builds prior to the fix, with ESR covered by the parallel Extended Support Release channel. The underlying defect is tracked in Mozilla Bugzilla issue 2069910, and the fixes shipped through the Mozilla Foundation Security Advisories MFSA2026-106, 2026-108, 2026-109, and 2026-110 (also catalogued as EUVD-2026-98518).
Know when Firefox gets its next vulnerability
- Watch products and get an email when something new is published
- Check this CVE against your own stack and servers
- Exploit and PoC references, threat intelligence from 22 sources
No credit card · 7-day full trial
Severity by source
AV:N/AC:H/PR:N/UI:R/S:C/C:H/I:H/A:H
Web-delivered so AV:N/PR:N with UI:R; race condition makes AC:H; sandbox escape breaks out of the content process giving S:C with full C/I/A impact.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Sandbox escape due to race condition in the Networking component. This vulnerability was fixed in Firefox 158 and Firefox ESR 153.5.
Executive ViewAI
A sandbox-escape flaw in Mozilla Firefox, the browser used across much of our workforce, could let attacker-controlled web content break out of the browser's protective sandbox and reach the underlying endpoint - meaning a single malicious page visit could escalate from a contained browser session to broader host compromise. The issue affects any employee browsing the web with an unpatched Firefox build, so the exposure footprint is essentially our entire internet-facing user population rather than a handful of servers. Leadership should care because this defeats a primary containment control on end-user devices, but exploitation is unreliable per attempt and no active exploitation or public exploit code has been observed, making this a manageable but urgent patching priority rather than an active incident.
Apply vendor patch.
Threat Intelligence Overview
How this decision was reached
The engine reads each signal below and applies a fixed list of rules from top to bottom. The first rule that matches sets the recommended action – like a statement, every line is shown.
What every action level means
SSVC AssessmentENISA
Priority Score
Attack Technique
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
Affected Products (CPE)CVE.org
Mozilla Firefox before 18.0, Firefox ESR 10.x before 10.0.12 and 17.x before 17.0.2, Thunderbird before 17.0.2, Thunderb
Use-after-free vulnerability in the serializeToStream implementation in the XMLSerializer component in Mozilla Firefox b
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi
The crypto.generateCRMFRequest function in Mozilla Firefox before 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird befo
The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with
The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi
The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se
Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and SeaMonkey before 2.25 allow remo
Integer underflow in the nsHtml5TreeBuilder class in the HTML5 string parser in Mozilla Firefox before 45.0 and Firefox
Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 do not properly restrict resource
Mozilla Firefox before 37.0 relies on docshell type information instead of page principal information for Window.webidl
The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for
EUVD-2026-98518
GHSA-mgh3-qw5r-mj83
NVD
CVE.org
EPSS
Exploit-DB