Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessAttacker hosts malicious page
-
DeliveryVictim loads page in Firefox
-
ExploitTrigger origin-validation flaw in DOM networking
-
ExecutionBypass site isolation boundary
-
ImpactRead cross-origin sensitive data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A07:2025 - Authentication Failures
ASVS 5.0
V6 - Authentication Origin validation
|
| Exploitation Conditions | Requires the victim to actively load attacker-controlled web content in an unpatched Firefox (before 157) or Firefox ESR (before 153.4); this user-interaction requirement (UI:R) is the primary limiting factor. The flaw lives in the DOM:Networking site-isolation path, so exploitation depends on the browser processing cross-origin network activity in the way the crafted page induces - no authentication and no special victim configuration is needed beyond running a vulnerable version with default settings. There is no server-side or zero-click remote trigger; the attacker cannot exploit a Firefox instance that never visits malicious content. |
| Impact | The input 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 that nonetheless requires user interaction - the victim must load attacker-controlled web content for Firefox's rendering engine to process. This is the realistic model for all browser-engine bugs and tempers the 8.1 score: there is no server-side or direct remote trigger. Exploitation signals point to LOW real-world urgency: EPSS is 0.15% (4th percentile), there is NO CISA KEV listing, and no public exploit code is identified. A CWE-346 (origin validation error) site-isolation defect in the DOM:Networking component is a cross-origin confidentiality/integrity concern rather than a memory-corruption RCE, and the C:H/I:H/A:N profile reflects cross-origin data exposure and potential cross-origin request/response tampering rather than code execution. The I:H in particular is on the generous side for a pure site-isolation leak and is vendor-assigned (reported by Mozilla); verify against MFSA detail. Net: a legitimate security fix worth patching in routine browser-update cadence, not an emergency - no evidence of active or imminent widespread exploitation. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page (or injects a malicious iframe/ad into a page the victim visits) that abuses the site-isolation / origin-validation weakness in Firefox's DOM networking layer. When the victim browses to the page, the flaw lets attacker-controlled content observe or influence data that should be isolated to another origin, enabling cross-origin disclosure of sensitive responses. No public proof-of-concept or exploit code has been identified. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Cross-origin data exposure and integrity compromise in Mozilla Firefox stem from a site-isolation failure in the DOM:Networking component, where origin boundaries are not correctly enforced, allowing attacker-controlled web content to reach resources and operations that should belong to a different origin. Affected are Firefox builds before 157 and Firefox ESR builds before 153.4; the issue is rated 8.1 HIGH (CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:H/A:N), meaning remote, unauthenticated, low-complexity exploitation that nonetheless requires the victim to load a malicious or compromised page. There is no public exploit identified at time of analysis and EPSS is very low at 0.15% (4th percentile), so real-world activity is not indicated, but the confidentiality and integrity impact is high once a user is lured to attacker-controlled content.
RemediationAI
Vendor-released patch: upgrade to Firefox 157 or Firefox ESR 153.4, or any later release on those channels, which resolves the DOM:Networking site-isolation flaw. Prioritize this on endpoints that routinely browse untrusted or user-supplied web content, and verify the installed version rather than relying on the updater's success, since ESR deployments are frequently pinned to a fixed baseline. Advisory references are https://www.mozilla.org/security/advisories/mfsa2026-100/, https://www.mozilla.org/security/advisories/mfsa2026-97/, https://www.mozilla.org/security/advisories/mfsa2026-101/ and https://www.mozilla.org/security/advisories/mfsa2026-103/, with technical detail at https://bugzilla.mozilla.org/show_bug.cgi?id=2068648. No configuration-level workaround fully replaces the patch; as compensating controls until upgrade, confirm strict site isolation is not disabled (verify about:config fission.autostart is left at its default enabled state, since disabling isolation would widen impact), restrict high-value authenticated sessions to a small allowlist of trusted origins to reduce exposure to lured navigation, and use policy or extension-based content blocking of unknown script sources - each of these lowers the chance of a victim reaching a crafted page but carries trade-offs such as broken functionality on legitimate multi-origin sites and increased user friction, and none of them removes the underlying origin-validation defect. Because the vector is PR:N, access controls and authentication hardening provide no meaningful protection here; the only reliable fix is patching.
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-346, Origin Validation Error, occurring inside Firefox's DOM:Networking code path. Firefox implements site isolation through its Fission architecture, which is intended to place content from different sites into separate processes and to enforce origin checks on all cross-origin navigation, subresource, and IPC operations. When the DOM:Networking component processes network activity without correctly validating the origin of the requesting or responding content, the isolation boundary between an attacker's page and a victim origin can be crossed, exposing data from the victim origin and, per the assessed vector, permitting modification of protected content (C:H/I:H). Because the weakness sits in the browser's networking-to-DOM boundary rather than in a specific web technology, it is not tied to a particular protocol or server configuration: any site the user visits is a potential delivery vector. The UI:R component of the vector reflects that the attacker cannot trigger the flaw against a browser that never renders hostile content, and PR:N confirms no credentials or privileged position on the target system are required.
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 auth, but victim must load a crafted page (UI:R); cross-origin disclosure and tampering give C:H/I:H, no availability impact, no scope change.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Site isolation issue in the DOM: Networking component. This vulnerability was fixed in Firefox ESR 153.4 and Firefox 157.
Executive ViewAI
Mozilla Firefox versions before 157 and Firefox ESR versions before 153.4 contain a high-severity site-isolation failure that can expose or corrupt data across origins when a user visits attacker-controlled content. This affects workforce users of affected Firefox builds and creates confidentiality and integrity risk for browser sessions and web-based business applications. No public exploit identified at time of analysis, and no vendor-released patch identified at time of analysis, so leadership should prioritize interim mitigations and monitor for a vendor fix.
No vendor-released patch identified at time of analysis; interim mitigations include enforcing enterprise browser policies, restricting affected Firefox builds for sensitive tasks, using alternative browsers for high-risk users, blocking untrusted content at the network layer, and monitoring vendor advisories for a 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-88795
GHSA-g257-qfqp-63c9
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB