Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted network content
-
ExploitTrigger buffer overflow in Networking component
-
ExecutionEscape content sandbox
-
ImpactExecute code outside sandbox (S:C)
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Bounds checking, buffer size validation
MITRE ATT&CK
2 techniques across 2 tactics: Execution, 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 or compromised web content in Firefox that reaches the vulnerable code path in the Networking component (UI:R) - there is no fully passive, no-interaction vector. No authentication is required (PR:N) and default configurations are affected, since this is a memory-safety defect in a core browser component rather than a feature that must be explicitly enabled. Limiting factors: the user-interaction requirement, the fact that a sandbox escape alone generally must be chained with a separate content-process code-execution primitive to achieve full host compromise, and that patched builds (Firefox 158 / ESR 153.5 and later) are not vulnerable. |
| Impact | This is a genuinely high-priority flaw despite several tempering signals. The CVSS 3.1 score of 9.6 (AV:N/AC:L/PR:N/UI:R/S:C, C:H/I:H/A:H) reflects a remotely reachable, low-complexity, unauthenticated memory-safety bug that breaks the browser sandbox (scope change) with full confidentiality, integrity, and availability impact. The only built-in brake is UI:R - a victim must be lured to attacker-controlled content. Counterbalancing the high CVSS: EPSS is only 0.19% (8th percentile), there is no CISA KEV listing and no public POC identified, so there is currently no evidence of active or imminent mass exploitation. The low EPSS alongside a high CVSS is typical for a freshly-patched browser sandbox escape - the risk is latent and depends on exploit development rather than demonstrated in-the-wild use. No signals conflict with the CVSS vector itself; the description ('sandbox escape in Networking component', buffer overflow) is fully consistent with AV:N and S:C. Note that a browser sandbox escape alone usually requires chaining with a content-process RCE to be weaponized end-to-end, which raises real-world exploitation complexity beyond what the raw score implies. SSVC framing: exploitation = none observed, automatable = no (requires user interaction/luring), technical impact = total. Verdict: patch promptly given ubiquity and total impact, but there is no evidence this is being exploited today. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page carrying malicious network-handling content and lures a victim into visiting it (UI:R). The crafted input triggers the buffer overflow in Firefox's Networking component, letting attacker code escape the content sandbox and run with the privileges of the browser process. No public exploit code has been identified at time of analysis, and a practical attack would typically need to be chained with a content-process code-execution bug. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
A sandbox escape in Mozilla Firefox's Networking component allows unauthenticated remote attackers to break out of the browser's security sandbox and potentially execute code on the host when a victim loads attacker-controlled web content. The vulnerability stems from incorrect boundary conditions (CWE-119) and carries a CVSS score of 9.6, though exploitation requires user interaction (UI:R) and the sandbox escape alone must be chained with a separate content-process code-execution primitive for full host compromise. No public exploit code has been identified, and the EPSS score is low at 0.19% (8th percentile); patched versions are Firefox 158 and Firefox ESR 153.5.
RemediationAI
Apply the vendor-released patch by upgrading to Firefox 158 or Firefox ESR 153.5 or later. These versions address the incorrect boundary conditions in the Networking component and eliminate the sandbox escape vulnerability. No specific workarounds are documented in the Mozilla advisories; however, because exploitation requires a victim to load malicious web content, restricting browsing to trusted sites and avoiding untrusted links can reduce exposure, though this is not a substitute for patching. Enterprises should deploy the update through their software management systems and verify version numbers after installation. For detailed instructions, refer to the Mozilla security advisories at https://www.mozilla.org/security/advisories/mfsa2026-106/, https://www.mozilla.org/security/advisories/mfsa2026-108/, https://www.mozilla.org/security/advisories/mfsa2026-109/, and https://www.mozilla.org/security/advisories/mfsa2026-110/, as well as the Bugzilla entry at https://bugzilla.mozilla.org/show_bug.cgi?id=2059151.
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
This is a memory-safety defect (CWE-119: Improper Restriction of Operations within the Bounds of a Memory Buffer) in the Networking component of Mozilla Firefox. Incorrect boundary conditions during network data processing can lead to out-of-bounds memory access, corrupting memory and enabling an attacker to escape the browser's sandbox. The sandbox is designed to isolate web content from the underlying operating system; a sandbox escape is a critical step that allows an attacker to run code with the privileges of the Firefox process, though full system compromise typically requires chaining with a separate remote code execution flaw in the content process. The CPE string cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* indicates that all versions prior to the fixes are potentially affected, with the vulnerability resolved in Firefox 158 and Firefox ESR 153.5. This issue was reported by Mozilla and is detailed in security advisories mfsa2026-106, mfsa2026-108, mfsa2026-109, and mfsa2026-110, as well as Bugzilla 2059151.
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:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Remotely reachable via malicious web content (AV:N) with no auth (PR:N) but requiring the victim to visit a page (UI:R); sandbox escape crosses a trust boundary (S:C) with total impact.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Sandbox escape due to incorrect boundary conditions in the Networking component. This vulnerability was fixed in Firefox 158 and Firefox ESR 153.5.
Executive ViewAI
A critical-severity sandbox escape in Mozilla Firefox's networking component could allow an attacker who lures an employee to attacker-controlled web content to break out of the browser's protective boundary - the first step toward running code on the underlying workstation. Firefox is broadly deployed across most enterprises, so unmanaged, outdated, or personally installed copies represent the primary exposure surface, and no vendor-released patch has been identified at time of analysis. No public exploit code has been identified at time of analysis, and full host compromise would require chaining this flaw with a separate content-process code-execution primitive, so the immediate risk is elevated but not yet demonstrated.
No vendor-released patch identified at time of analysis. Interim mitigations: migrate users to Firefox ESR 153.5 once that fixed build is confirmed available; enforce browser hardening policy (disable unneeded plugins and extensions, restrict script and download behavior); block untrusted and newly registered domains at the secure web gateway and DNS layer; maintain EDR coverage with browser child-process monitoring; segment endpoints to limit lateral movement from any compromised host; and reinforce user awareness against attacker-controlled web content, since exploitation requires user interaction.
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
A buffer overflow occurs when a program writes more data to a memory buffer than it was allocated to hold, causing the excess data to spill into adjacent memory regions.
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-98485
GHSA-589f-33q5-grw7
NVD
CVE.org
EPSS
Exploit-DB