Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
DeliveryDeliver crafted graphics content
-
ExploitTrigger uninitialized memory in Graphics component
-
ExecutionEscape content sandbox (scope change)
-
ImpactDisclose limited memory / affect host
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Variable initialization
|
| Exploitation Conditions | Exploitation requires the victim to use Mozilla Firefox and to visit or render attacker-controlled web content that exercises the vulnerable Graphics component (UI:R - user interaction such as navigating to a malicious page is mandatory). No authentication or prior privileges are needed (PR:N), and default configurations are affected since the Graphics component is a core rendering path. The principal limiting factor is the required user interaction, which prevents fully automated, zero-click mass exploitation; additionally, only unpatched versions below Firefox 158 / ESR 115.43 / ESR 153.5 are affected, and the Low impact metrics constrain the practical payoff of a successful exploit. |
| Impact | This is a moderate-severity, low-priority issue in practice. The vendor CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:L/I:L/A:L, base 7.1) describes a network-reachable, low-complexity, unauthenticated bug that requires user interaction (UI:R) - consistent with a browser flaw triggered by visiting a malicious page - with a scope change (S:C) that aligns with the described sandbox escape crossing the content-process boundary. However, the impact metrics are all Low (C:L/I:L/A:L), not High, which tempers the raw score. Exploitation signals are weak and mutually reinforcing: EPSS is only 0.19% (8th percentile), the CVE is NOT in CISA KEV, and no public exploit code was identified in the provided data. There is no conflict between signals - all of them point to low real-world exploitation likelihood. One minor tension worth noting: the description calls this a 'Sandbox escape' while the input Tags label it 'Information Disclosure'; the Low confidentiality impact and CWE-908 (uninitialized memory) make limited information disclosure plausible, but a full sandbox escape typically implies broader consequences than the C:L/I:L/A:L vector suggests - verify scope of impact against the Mozilla advisories. Net: a legitimate memory-safety bug to patch on normal browser-update cadence, not an emergency. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted graphics content that triggers use of uninitialized memory in Firefox's Graphics component. When a victim visits the page (UI:R), the flaw allows the attacker to cross the browser sandbox boundary and leak limited memory contents or affect host-side state. No public proof-of-concept or exploit code was identified in the available data. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 16, 2026
Sandbox escape in the Mozilla Firefox Graphics component allows an attacker who can get a victim to render attacker-controlled web content to break out of the browser's content-process sandbox, with Low-rated confidentiality, integrity and availability impact but a changed security scope. Affected are unpatched Firefox builds below 158 and ESR builds below 115.43 and 153.5; no authentication is required, but exploitation is gated by mandatory user interaction (UI:R) such as visiting a crafted page, which precludes zero-click mass exploitation. There is no public exploit identified at time of analysis and no CISA KEV listing, and the EPSS score is very low at 0.19% (8th percentile), making this a moderate-severity but low-priority issue in practice; vendor-released patches are available.
RemediationAI
Vendor-released patch: upgrade to Mozilla Firefox 158, Mozilla Firefox ESR 115.43, or Mozilla Firefox ESR 153.5, depending on the branch in use; these are the exact fixed versions named in the advisory. Apply the update through the normal browser update channel or your software distribution tooling, and verify the reported version after restarting the browser, since ESR installs on managed endpoints often lag and must be targeted explicitly. Mozilla's advisories mfsa2026-106, mfsa2026-107, mfsa2026-108, mfsa2026-109 and mfsa2026-110 document the fixes, and the technical record is at https://bugzilla.mozilla.org/show_bug.cgi?id=2068420. No specific workaround for this Graphics component issue is documented in the available references, and because the flaw sits on a core rendering path there is no supported configuration switch that reliably removes exposure without also breaking normal browsing; the practical compensating controls are to restrict browsing of untrusted web content where operationally feasible and to ensure the browser runs with its normal sandbox enabled rather than in a reduced-sandbox compatibility mode, which would only widen the impact of a successful escape. Given the required user interaction, no public exploit identified at time of analysis, and the 0.19% EPSS score, this can be scheduled within a routine patch cycle rather than an emergency one, though internet-facing and high-value browsing endpoints should be prioritized.
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 root cause class is CWE-908, Use of Uninitialized Resource: memory in the Firefox Graphics rendering path is consumed before it has been initialized, and the resulting uninitialized or stale value drives a sandbox escape. Firefox relies on a multi-process architecture in which untrusted web content is parsed and rendered in a heavily restricted content/GPU process that is isolated from the parent process and the host operating system; the Graphics component bridges that boundary by handing compositing and rasterization work across process lines. When a graphics routine operates on uninitialized memory, it can produce attacker-influenced state or values that cross the privilege boundary, letting the compromised content process affect code running with higher privileges - the reason the CVSS vector carries S:C (scope change) despite Low C/I/A metrics. The narrow, Low-rated impact triple indicates the primitive gives limited read/write or informational leverage rather than a clean, high-fidelity arbitrary code execution path, and the EPSS percentile of 8% reflects both that modest payoff and the required user interaction. Engineering references point to Mozilla Bugzilla issue 2068420 and security advisories mfsa2026-106 through mfsa2026-110, which cover the release and ESR branches in which the flaw was corrected.
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:L/I:L/A:L
Web-delivered bug needs no privileges (PR:N) but requires visiting a page (UI:R); sandbox escape crosses a trust boundary (S:C); uninitialized-memory impact is limited, so C/I/A all Low.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Sandbox escape due to uninitialized memory in the Graphics component. This vulnerability was fixed in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5.
Executive ViewAI
Unpatched Mozilla Firefox and Firefox ESR installations across the organization are exposed to a sandbox-escape flaw in the browser's Graphics component (CVE-2026-109712) that allows a crafted web page to break out of the content-process sandbox, with a changed security scope that undermines a key containment layer. Because Firefox is a standard productivity tool on most endpoints, any employee who visits a malicious or compromised site is a potential entry point, making this a broad workforce exposure rather than an isolated server issue. There is no public exploit identified at time of analysis, no confirmed active exploitation, and the EPSS score is very low, so this should be handled as a routine but time-boxed patch-management priority rather than an emergency.
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.
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-98637
GHSA-qprj-mxfp-87w7
NVD
CVE.org
EPSS
Exploit-DB