Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
ExploitTrigger boundary error in Layout engine
-
ExecutionCorrupt or over-read adjacent memory
-
ImpactLeak limited data or tamper with content
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 a victim using Mozilla Firefox prior to version 158 to load attacker-controlled web content that exercises the vulnerable Layout component code path - the UI:R metric confirms user interaction (visiting or rendering the malicious page) is mandatory. No authentication or special privileges are needed (PR:N), and default Firefox configurations are affected since the Layout engine is core rendering functionality. The principal limiting factors are the required user interaction and the inherently bounded impact (low confidentiality, low integrity, no availability), meaning an attacker cannot act fully remotely without enticing the user and cannot, per vendor scoring, achieve code execution or denial of service from this flaw alone. |
| Impact | Signals are consistent and point to a moderate, not urgent, priority. The vendor CVSS of 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) describes a network-reachable, low-complexity, unauthenticated flaw that nonetheless REQUIRES user interaction (UI:R) and yields only low confidentiality and low integrity impact with no availability impact. EPSS reinforces low real-world risk at 0.15% (4th percentile), the flaw is NOT in CISA KEV, and no public exploit has been identified, so there is no evidence of active or imminent exploitation. No SSVC decision vector was supplied in the input, so automatable/technical-impact cannot be independently cross-referenced. The one tension worth noting: this is a CWE-119 memory-boundary defect (tagged Buffer Overflow) in a browser's Layout engine, a class that can sometimes be escalated, yet the vendor scored impact as only partial (C:L/I:L, A:N) rather than code execution - suggesting the boundary error leaks or corrupts limited memory rather than granting full control. Net: a routine browser memory-safety fix to be patched via normal update cadence, not an emergency. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page with crafted content that triggers the incorrect boundary condition in Firefox's Layout component, then lures a victim running a pre-158 Firefox to visit it. When the page renders, the out-of-bounds access leaks small amounts of adjacent memory or corrupts layout state, consistent with the low confidentiality/integrity impact. No public exploit code has been identified, and exploitation depends on the user actually loading the attacker's page (UI:R). |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
Incorrect boundary conditions in Mozilla Firefox's Layout component prior to version 158 allow remote, unauthenticated attackers to cause low-severity confidentiality and integrity impact by enticing a user to render attacker-controlled web content; the assessed CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) confirms that user interaction is mandatory and that availability is not affected. No public exploit code has been identified and there is no CISA KEV entry at time of analysis, while the EPSS score is low at 0.15% (4th percentile), consistent with a moderate, not urgent, priority. The flaw is a memory-buffer boundary error (CWE-119) fixed in Firefox 158.
RemediationAI
Vendor-released patch: Firefox 158. Users and administrators should upgrade to Firefox 158 or later; Mozilla's advisories at https://www.mozilla.org/security/advisories/mfsa2026-106/ and https://www.mozilla.org/security/advisories/mfsa2026-109/ detail the fix, and Bugzilla 2069765 (https://bugzilla.mozilla.org/show_bug.cgi?id=2069765) tracks the underlying change. Because exploitation requires the victim to load attacker-controlled content in the Layout engine, no feature toggle fully eliminates the risk without breaking rendering; the most effective compensating control before patching is restricting browsing to trusted sites or enforcing enterprise policies that block untrusted content, though this carries a significant usability trade-off. The moderate EPSS score (0.15%, 4th percentile) and the absence of public exploit code mean urgency is moderate, but applying the Firefox 158 update remains the definitive remediation.
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 vulnerability resides in Mozilla Firefox's Layout engine, the core Gecko subsystem responsible for parsing HTML/CSS and computing element geometry, positioning, and rendering. CWE-119 (Improper Restriction of Operations within the Bounds of a Memory Buffer) describes the root cause: incorrect boundary conditions in the Layout component permit out-of-bounds memory access, and the CVE is tagged as a Buffer Overflow. The CPE string cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* indicates that all Firefox versions before 158 are potentially affected. Because the Layout engine processes web content delivered to the browser, exploitation is client-side and triggered when a user loads a crafted page; the assessed vector AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N reflects that the attack surface is network-reachable but constrained by mandatory user interaction and bounded to low confidentiality and low integrity impact with no availability loss. Mozilla advisories MFSA2026-106 and MFSA2026-109, along with Bugzilla issue 2069765, document the fix landing in Firefox 158.
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:L/I:L/A:N
Web-delivered Layout flaw reachable over the network with no privileges but requiring the user to load malicious content (UI:R); memory boundary error yields only partial confidentiality/integrity and no availability impact.
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.
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-98489
GHSA-h9v8-63qj-vhv8
NVD
CVE.org
EPSS
Exploit-DB