Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost malicious web page
-
DeliveryLure victim to visit page (UI:R)
-
ExploitTrigger undefined behavior in DOM Streams
-
ExecutionCorrupt or read browser memory
-
ImpactDisclose sensitive data / alter state
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Reliance on undefined/unspecified behavior
|
| Exploitation Conditions | Requires the victim to load attacker-controlled web content in an unpatched Firefox (UI:R) that exercises the DOM Streams API path triggering the undefined behavior; no authentication and no special browser configuration is needed (PR:N, default configuration). Limiting factors: exploitation is client-side and cannot proceed without user interaction (visiting a page or opening crafted content), and affected builds are those prior to Firefox 157, ESR 153.4, ESR 140.17, and ESR 115.42 - patched versions are not exploitable. As a CWE-758 memory-safety-class bug, reliable weaponization typically requires meaningful exploit-development effort, consistent with the very low EPSS. |
| Impact | Signals are mixed and point to moderate real-world priority rather than an urgent emergency. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N, 8.1 High) describes a network-reachable, low-complexity, unauthenticated flaw requiring user interaction - i.e. a victim must visit attacker-controlled web content - with high confidentiality and integrity impact but no availability impact. Against that, EPSS is very low at 0.16% (4th percentile), there is no CISA KEV listing, and no public exploit was identified at time of analysis, so there is no public exploitation signal. CWE-758 (reliance on undefined behavior) in the DOM Streams component is a memory-safety-class issue typical of browser advisories; such bugs are often exploitable in principle but require nontrivial development to weaponize, which is consistent with the low EPSS. The 'Information Disclosure' tag understates the vector, which also carries I:H (integrity), so impact is not confidentiality-only. Net: a genuinely High-severity client-side browser flaw worth prompt patching given Firefox's footprint, but not a drop-everything issue absent any exploitation evidence. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page that exercises the DOM Streams code path in a way that triggers undefined behavior in Firefox. A victim using an unpatched Firefox browser visits the page (UI:R), and the resulting memory-corruption/undefined-behavior condition is leveraged to disclose sensitive in-process data and/or corrupt browser state. No public proof-of-concept or active exploitation has been identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Undefined behavior in the DOM Streams component of Mozilla Firefox allows remote, unauthenticated attackers to trigger memory-safety-class corruption in the browser process when a victim loads attacker-controlled web content, yielding high confidentiality and integrity impact (CVSS 3.1 base 8.1, AV:N/AC:L/PR:N/UI:R). The flaw affects builds prior to Firefox 157, Firefox ESR 153.4, Firefox ESR 140.17, and Firefox ESR 115.42, and requires user interaction - the victim must open a crafted page that exercises the vulnerable Streams API path - but no authentication or non-default browser configuration is needed. No public exploit code has been identified at time of analysis and CISA KEV does not list this issue; EPSS is very low at 0.16% (4th percentile), though the underlying CWE-758 memory-safety class means reliable weaponization would require substantial exploit-development effort rather than being trivially scriptable.
RemediationAI
Vendor-released patch: upgrade to Firefox 157 (mainline), Firefox ESR 153.4, Firefox ESR 140.17, or Firefox ESR 115.42 - whichever matches the installed branch - using the built-in updater or the packages from https://www.mozilla.org/security/advisories/ (mfsa2026-97 through mfsa2026-103). Verify completion by checking Help > About Firefox for the exact fixed version, and note that ESR 115.42 is the only remediation for hosts pinned to the legacy 115 branch, so environments that have frozen that branch must schedule the update rather than relying on 140.x/153.x installs elsewhere. Enterprise administrators should force an update check via the Mozilla Update policy or their software-deployment tooling and confirm that Firefox is not version-pinned by configuration. Where patching must be deferred, the practical trade-off is to restrict browsing to trusted origins and disable or block untrusted script execution with an extension such as NoScript or an enterprise content-filtering proxy, which reduces exposure to the crafted Streams-driven page but degrades general web usability and is not a reliable substitute for patching. Disabling JavaScript outright (about:config javascript.enabled=false) neutralizes the reachable attack surface but breaks the majority of modern sites; browser sandboxing, site isolation, and keeping the renderer sandbox enabled remain useful damage-limitation controls rather than fixes. Mozilla has not published a per-configuration workaround that blocks the vulnerable Streams path, and no public exploit code has been identified, so patching remains the primary and recommended action.
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 lives in Firefox's implementation of the DOM Streams API, the JavaScript-accessible abstraction (ReadableStream, WritableStream, TransformStream) used by the web platform for incremental data handling such as fetch response bodies and file reads. CWE-758 (Reliable Code of a Non-Standard or Undefined Behavior) indicates the root cause is a code path whose behavior is not well defined - typically an unhandled edge case in stream state transitions, queue/backpressure handling, or chunk transfer - which in a native browser engine can manifest as type confusion, use-after-free, or out-of-bounds access rather than a merely cosmetic glitch. Because Streams are reachable from ordinary page script, a website the victim visits can drive the component into the undefined state; the CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N) confirms the trigger is network-delivered, low complexity, requires no privileges, needs only the victim to load the content, and stays within the browser's security scope while compromising confidentiality and integrity (the Common Weakness Enumeration, CWE-758, and the Streams component attribution come from the CVE record; the CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* marks all unpatched Firefox builds as the affected product family).
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
Web-delivered client-side flaw needing only a page visit: AV:N/AC:L/PR:N/UI:R; undefined behavior yields high confidentiality and integrity impact with no availability effect, in-process so S:U.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Undefined behavior in the DOM: Streams component. This vulnerability was fixed in Firefox ESR 153.4, Firefox 157, Firefox ESR 115.42, and Firefox ESR 140.17.
Executive ViewAI
A memory-safety flaw in Mozilla Firefox's DOM Streams component (CVE-2026-100771, CVSS 8.1) allows a crafted web page to corrupt the browser process, putting the confidentiality and integrity of anything a user does in that session at risk. Because Firefox is broadly deployed across the workforce and the trigger is simply loading hostile content - no credentials, elevated privileges, or non-default configuration required - any employee who browses the web is a potential entry point, and no vendor-released patch has been identified at the time of analysis. Leadership should treat this as an unpatched, high-severity browser exposure that demands interim mitigation and heightened detection rather than a routine update cycle.
No vendor-released patch identified at time of analysis. Interim mitigations: constrain browsing of untrusted or newly registered sites via network-layer filtering; keep site isolation, tracking protection, and sandboxing features enabled and avoid weakening them through policy; run browsers under standard-user (non-administrative) accounts to limit post-exploitation escalation; deploy crash and process-anomaly telemetry to detect browser memory-corruption attempts; and monitor Mozilla's advisory channel daily so a vendor fix is applied the moment it is published.
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-88923
GHSA-27h8-27q2-7ppf
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB