Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted layout content
-
ExploitTrigger boundary error in Layout engine
-
ExecutionCorrupt renderer process memory
-
ImpactExecute code in content sandbox
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 use an affected, unpatched version of Firefox (prior to 158) or Firefox ESR (prior to 115.43 or 153.5) and to actively load attacker-controlled web content - the CVSS UI:R and the client-side browser context mean the user must navigate to or render a malicious page for the Layout boundary condition to be triggered. No authentication is required (PR:N) and no special non-default Firefox configuration is indicated by the description, but the mandatory user interaction (visiting/rendering hostile content) is the primary factor limiting mass exploitation; there is no server-side or passive network vector. |
| Impact | This is a memory-safety flaw (incorrect boundary conditions, CWE-119) in Firefox's Layout engine, carrying a vendor CVSS of 8.1 (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N). The CVSS vector signals a network-reachable, low-complexity, unauthenticated bug that nonetheless requires user interaction (UI:R) - consistent with a victim being lured to a malicious web page rather than wormable server-side exploitation. Counterbalancing the high CVSS, the EPSS score is very low at 0.16% (5th percentile), there is no CISA KEV listing, and no public exploit code is referenced in the provided data - so despite the high severity rating, no evidence of active or imminent exploitation exists at time of analysis. One internal inconsistency worth noting: the vendor marks A:N (no availability impact), which is unusual for a buffer-overflow/memory-corruption class bug that typically at minimum crashes the renderer; the C:H/I:H rating implies potential code execution, which usually carries availability impact as well - verify exact impact with Mozilla's advisory. Net assessment: a legitimately serious client-side browser bug given Firefox's enormous install base, but current real-world risk is moderated by the required user interaction and the absence of any exploitation or POC signal - patch on normal browser-update cadence rather than emergency timelines unless exploitation emerges. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page containing specially crafted content that triggers the incorrect boundary condition in Firefox's Layout component when rendered. A victim running an unpatched Firefox visits the page (the UI:R user interaction), causing memory corruption that could lead to disclosure of in-process memory or arbitrary code execution in the content process. No public exploit code is identified at time of analysis, so this scenario is inferred from the CWE-119 class and CVSS vector rather than a demonstrated exploit. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Memory corruption in Mozilla Firefox's Layout engine lets a remote, unauthenticated attacker who convinces a victim to render attacker-controlled web content corrupt memory, with the assessed vector (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:H) indicating high confidentiality and integrity impact and a full availability impact on the client. All Firefox builds prior to 158 are affected, along with Firefox ESR releases prior to 115.43 and 153.5. Exploitation hinges entirely on user interaction - the victim must navigate to or render a hostile page - and no public exploit or active exploitation has been identified at time of analysis; EPSS is low at 0.16% (5th percentile), and vendor-released fixes (Firefox 158, ESR 115.43, ESR 153.5) are available per Mozilla advisories mfsa2026-106 through mfsa2026-110.
RemediationAI
Apply the vendor-released patch: upgrade to Firefox 158 on the mainline channel, or to Firefox ESR 115.43 or Firefox ESR 153.5 on the corresponding ESR branches - these are the exact fixed versions named in the advisory set (MFSA 2026-106 through MFSA 2026-110, cross-referenced in Bugzilla 2068441). Because the fix must be delivered as a browser binary update, prioritize rapid deployment through your patch management or enterprise policy tooling (e.g., forced update policies for managed Firefox/ESR fleets) since users will not self-update reliably. No vendor workaround exists for this Layout boundary condition, and the practical compensating controls are limited and carry real trade-offs: restricting browsing to a hardened allow-list of trusted sites reduces exposure to attacker-controlled pages but breaks general web use; disabling JavaScript via about:config (javascript.enabled=false) would blunt many memory-corruption exploit chains but severely degrades functionality and is not confirmed to block this specific Layout path; and running Firefox in a heavily sandboxed or disposable VM/container limits post-exploitation impact but does not prevent the memory-safety trigger. Note that neither a public exploit nor active exploitation has been identified at time of analysis, and the required user interaction (UI:R) lowers mass-exploitation likelihood, so aggressive mitigations should be weighed against their operational cost. Verify the about:support version string after upgrading to confirm the build is at 158 or the appropriate ESR baseline.
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 an incorrect-boundary-condition defect (CWE-119) in Firefox's Layout component, the engine subsystem responsible for computing box geometry, reflow, and rendering of the DOM/CSS tree. When Layout calculates or validates the bounds of a structure while processing attacker-supplied markup and styles, the boundary check is insufficient, producing an out-of-bounds memory operation that can be shaped into corruption of heap or object state. Mozilla classifies and addresses this class of issue under its memory-safety bug program, and the fix landed alongside Bugzilla 2068441 across three release trains (mainline 158 plus ESR 115.43 and 153.5), which is consistent with a code path reachable from ordinary page rendering rather than a privileged browser API. The CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* confirms the target is the general Firefox browser product; the CVSS vector's PR:N shows no authentication is needed, while UI:R confirms the attacker cannot trigger the condition passively - the browsing context must actively load the crafted content. This is a client-side rendering surface: there is no server-side component, and the attack does not propagate over the network without a victim's browser fetching and rendering the malicious material.
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:N
Network-delivered web content, no privileges, but user must load a malicious page (UI:R); memory corruption plausibly yields code execution and renderer crashes, so C/I/A all High (A raised from vendor's N).
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Incorrect boundary conditions in the Layout component. This vulnerability was fixed in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5.
Executive ViewAI
A memory-corruption flaw in Mozilla Firefox's Layout engine exposes every employee who browses the web with an unpatched browser - including Firefox ESR builds used on managed endpoints - to potential data theft, tampering, and full browser crashes if they simply open a malicious page. Because success depends on a user visiting hostile content rather than on credentials or network position, the effective attack surface is ordinary day-to-day web browsing across the workforce. Leadership should care less about the exploit's current maturity (no public exploit or active exploitation has been identified at time of analysis) and more about the sheer install base and the fact that remediation is a routine browser update that can be completed quickly at low cost.
Apply vendor patch. If Firefox 158, ESR 115.43, or ESR 153.5 cannot be deployed immediately to a given endpoint, interim mitigations include restricting browsing on that device to approved sites, blocking script execution through enterprise policy or a script-blocking extension, enabling site isolation, and monitoring for abnormal browser crashes that could indicate memory-corruption attempts.
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-98651
GHSA-qrr3-f9g6-cf9g
NVD
CVE.org
EPSS
Exploit-DB