Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure user to malicious web page
-
DeliveryDeliver crafted sandbox-escape content
-
ExploitTrigger flaw in process sandboxing component
-
ExecutionEscape content-process confinement
-
ImpactDisclose sensitive data and escalate privileges
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery 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 run an unpatched Firefox (before 158) or Firefox ESR (before 153.5) and to actively load attacker-controlled web content, satisfying the CVSS UI:R requirement - it is not a server-side or self-propagating flaw. The vulnerability lies in the Process Sandboxing component, so a successful attack must break the content-process sandbox boundary; no attacker authentication is needed (PR:N). Limiting factors: mandatory user interaction (opening/rendering malicious content), the need for an unpatched version, and the absence of any observed automation path (SSVC Automatable: no), which together constrain this to targeted, user-driven attacks rather than mass exploitation. |
| Impact | This is a genuinely high-priority client-side vulnerability. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) scores 8.8 and indicates a network-reachable, low-complexity flaw requiring no attacker privileges but DOES require user interaction (UI:R) - consistent with a browser flaw triggered by visiting a malicious page. The affected component is the Process Sandboxing security boundary, so a successful exploit undermines a core defense-in-depth layer, yielding total technical impact (per CISA SSVC: Technical Impact total), which aligns with the combined Information Disclosure and Privilege Escalation outcomes and the high C/I/A ratings. However, the signals are not uniformly alarming: SSVC lists Exploitation as 'none' and Automatable as 'no', meaning no observed exploitation and no reliable mass-automation path (expected, since UI:R forces a human to open attacker content). There is no CISA KEV listing and no public exploit code identified in the provided data, and no EPSS probability was supplied. The CWE-200 (Information Exposure) classification somewhat understates the full impact given the description also cites privilege escalation. Net: a sandbox-escape in a mass-market browser warrants prompt patching, but current evidence points to latent/unexploited risk rather than active, wormable attack. |
| Exploit ScenarioDerived | An attacker lures a user into visiting a malicious or compromised web page in an unpatched Firefox build; crafted content abuses a flaw in the process sandboxing layer to escape the content-process confinement, read sensitive data from other contexts, and escalate privileges on the host. No public proof-of-concept was identified at time of analysis, and the attack requires the victim to actively load the attacker-controlled content (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Privilege escalation and information disclosure in Mozilla's Process Sandboxing component let attacker-controlled web content break out of the Firefox content-process sandbox on unpatched installations - Firefox before 158 and Firefox ESR before 153.5 - with high confidentiality, integrity and availability impact (CVSS 3.1 base 8.8, AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H). Exploitation is remote and requires no attacker authentication, but it is user-driven: the victim must actively load the malicious page, and CISA's SSVC assessment records Exploitation: none and Automatable: no, so this is a targeted client-side risk rather than a mass-exploitation candidate. There is no public exploit identified at time of analysis, and vendor-released fixes ship in Firefox 158 and Firefox ESR 153.5 (MFSA 2026-106 and MFSA 2026-108).
RemediationAI
Apply the vendor-released patches: upgrade Firefox to 158 or later, and upgrade Firefox ESR to 153.5 or later - these are the exact versions named in MFSA 2026-106 and MFSA 2026-108. Firefox's automatic update mechanism normally delivers these builds without user action, so the priority action for administrators is to confirm the update has actually been applied on managed endpoints and to verify the reported version, because the exploit requires only that the victim load attacker-controlled web content on a still-unpatched build. No vendor workaround that removes the underlying sandbox flaw is documented in the supplied references, and no CVE-level mitigation is offered in the advisories. Until an update can be deployed, compensating controls should target the prerequisite rather than the bug: confine browsing of untrusted or unsolicited links to a disposable VM, an OS-level sandboxed container, or a separate managed browser profile with no access to corporate credentials and no persistent storage; the trade-off is reduced usability and possible breakage of SSO or certificate-based workflows. Reducing the attack surface further by disabling unnecessary extensions and avoiding high-risk content on unpatched clients helps only marginally, since any rendered page can trigger the defect, and disabling the JavaScript JIT or similar hardening carries a significant browsing-performance penalty while still not repairing the process-sandbox weakness. Blocking network egress to untrusted sites or forcing all web access through a hardened, separately patched browser are viable stop-gaps where the update cannot be staged immediately, at the cost of restricting legitimate user activity.
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 lives in Firefox's Process Sandboxing component, the multi-process architecture in which web content is rendered inside a low-privilege content process that is isolated from the browser's parent process and from the operating system. A successful attack must therefore cross that sandbox boundary, escalating the attacker's footprint from a compromised renderer to something with parent-process or OS-level reach. The root-cause class is CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor): data handled inside the sandbox is exposed to a context that should not be able to read it, and that disclosure is the lever used to achieve the privilege-escalation effect tagged in the advisory metadata. Because the boundary itself is the target, the weakness is independent of any specific web technology - HTML, JavaScript or media parsing all serve equally well as the delivery vector - and the CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* confirms the affected surface is the Firefox browser (including the ESR channel) rather than a server-side or networked service. The CVSS vector (PR:N, UI:R) is consistent with this: any remote web page is a candidate trigger, but only when a human actually renders it, and the SSVC evaluation of Technical Impact: total reflects that a defeated sandbox yields broad read/write/execute capability inside the browser's trust domain. Mozilla's Bugzilla record (bug 2067976) and the two MFSA advisories are the authoritative technical references.
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:U/C:H/I:H/A:H
Network-delivered browser content with no attacker privileges (PR:N) but mandatory victim interaction (UI:R); sandbox escape yields high confidentiality, integrity, and availability impact.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Information disclosure, privilege escalation in the Security: Process Sandboxing component. This vulnerability was fixed in Firefox 158 and Firefox ESR 153.5.
Articles & Coverage 1
Executive ViewAI
A sandbox-escape vulnerability in Mozilla Firefox (all versions before 158 and Firefox ESR before 153.5) allows malicious web content to break out of the browser's process sandbox and compromise the host endpoint, affecting confidentiality, integrity, and availability. Because Firefox is broadly deployed across knowledge-worker and engineering fleets, a single employee loading a crafted page on an unpatched device could expose that endpoint and any credentials or data reachable from it. Exploitation is user-driven and targeted rather than automated, and no public exploit has been identified at time of analysis, so leadership should treat this as a manageable but time-bound remediation priority rather than an emergency.
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
Privilege escalation occurs when an attacker leverages flaws in access control mechanisms to gain permissions beyond what they were originally granted.
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
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-98486
GHSA-c4mq-cc7v-mw2m
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB