Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessHost crafted malicious web page
-
DeliveryVictim loads page in unpatched Firefox
-
ExploitTrigger DOM:Security mitigation bypass
-
ExecutionChain with content-process bug
-
ImpactCross-boundary read/modify data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Protection mechanism completeness
|
| Exploitation Conditions | Requires an unpatched Firefox (before 157) or Firefox ESR (before 153.4), and the victim must actively load attacker-controlled web content that exercises the DOM:Security mitigation bypass (UI:R - drive-by via a malicious or compromised page). No authentication is required of the attacker (PR:N). The practical limiting factor is that this is a mitigation/defense-in-depth bypass (CWE-693): defeating the protection generally yields full impact only when combined with a separate content-process vulnerability, so it is a weakening primitive rather than a self-contained compromise. No special victim configuration is indicated beyond running a vulnerable version. |
| Impact | Signals conflict sharply. The vendor-assigned CVSS 3.1 is 9.6 (Critical) with AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, but every exposure signal points the other way: EPSS is 0.15% (4th percentile), there is no CISA KEV listing, no public POC, and CISA SSVC records Exploitation: none and Automatable: no (only Technical Impact: total aligns with the high CVSS). The 9.6 is driven largely by the scope change (S:C) and full CIA impact, which for a browser 'mitigation bypass' (CWE-693) is optimistic - a protection-mechanism bypass defeats a defense-in-depth layer and typically must be CHAINED with a separate content-process memory-corruption bug to actually achieve C:H/I:H/A:H. On its own it weakens a mitigation rather than directly compromising data. Realistically this is an important-to-patch browser flaw but not an emergency: no active exploitation, requires victim interaction (UI:R, loading a crafted page), and the headline severity overstates standalone impact. Note: the PR:N/UI:R combination is consistent with a drive-by web-content bug. |
| Exploit ScenarioDerived | An attacker hosts a malicious or compromised web page that exercises the crafted DOM content needed to bypass the DOM:Security mitigation; a victim running an unpatched Firefox/ESR visits it. The bypass neutralizes a browser defense-in-depth protection, which the attacker then pairs with a content-process exploit to read/alter data across the normal security boundary. No public exploit code is identified at time of analysis, and CISA SSVC lists exploitation as none. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 01, 2026
Unauthenticated remote attackers can bypass a DOM:Security mitigation in Mozilla Firefox (versions before 157 and Firefox ESR before 153.4) by enticing a victim to load attacker-controlled web content, defeating a browser protection mechanism rather than exploiting a memory-safety bug directly. The CVSS 3.1 vector (AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H, score 9.6) and a scope change indicate high potential confidentiality, integrity and availability impact once the defense is circumvented, but the independent assessment characterizes this as a weakening primitive: full impact generally requires chaining with a separate content-process vulnerability, so it is not a self-contained compromise. Exploitation signals conflict sharply - a critical-looking CVSS score against an EPSS of only 0.15% (4th percentile), a CISA SSVC rating of Exploitation: none / Automatable: no, and no public exploit identified at time of analysis; there is no confirmed actively exploited (CISA KEV) status.
RemediationAI
Upgrade to a fixed release: Mozilla Firefox 157 or Firefox ESR 153.4, per the vendor advisories at https://www.mozilla.org/security/advisories/mfsa2026-97/ and https://www.mozilla.org/security/advisories/mfsa2026-100/ (additional fix context in mfsa2026-101 and mfsa2026-103, with the underlying issue tracked at https://bugzilla.mozilla.org/show_bug.cgi?id=2066321). Because the fix is covered by Firefox's standard update channel, enterprises should force the update with an enterprise policy that pins the minimum allowed version and disables update deferral, and verify reported versions from endpoint telemetry rather than relying on self-reported user updates. If an immediate fleet-wide upgrade is not possible, the trade-offs are modest given the exploitation picture: EPSS is 0.15% (4th percentile) and SSVC rates Exploitation: none with Automatable: no, and because this is a defense-in-depth weakening that only yields full impact when chained with a separate content-process flaw, a short staged rollout is a reasonable risk decision. Interim compensating controls, in order of practicality: set Enhanced Tracking Protection and content blocking to Strict so known-malicious and injected-content hosts are blocked before the bypass can be exercised (side effect: third-party scripts and some embedded content on legitimate sites break); restrict high-risk browsing profiles to an allowlist of trusted origins for users who do not need general web access (side effect: significant usability loss, not viable for general staff); and disable or gate unnecessary plug-in/extension and script-heavy workflows on managed endpoints. Given that this is a weakening primitive, treat any subsequent Firefox content-process memory-corruption advisory as an urgent chained-exploitation risk and prioritize patching it immediately, and monitor vendor advisories and EPSS/KEV feeds for a change in exploitation status that would justify emergency out-of-band upgrades.
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 classified as CWE-693 (Protection Mechanism Failure) and lives in the DOM:Security component that implements Firefox's in-browser defensive controls - the checks that enforce same-origin policy, block mixed/insecure content, constrain script execution, and otherwise keep web content inside its intended security boundary. Because the affected code is a mitigation layer rather than a parser or JIT engine, the bug is a bypass: attacker-supplied page content gets to operate as though a protection were present when it is not. The scope-changed (S:C) rating reflects that a failure in this component affects resources beyond its own security scope, and the metrics (network vector, no privileges, but user interaction) describe a drive-by delivery model in which the victim simply has to open a malicious or compromised page. An independent assessment notes the practical limiting factor: defeating a defense-in-depth control typically converts into full compromise only when combined with a separate content-process vulnerability, making this a precondition for exploitation rather than a complete attack on its own. Notably, the intelligence tags label this an authentication bypass while the description, CWE and advisory framing describe a mitigation bypass; the CWE-693 and DOM:Security context is the more consistent interpretation. Mozilla's CPE entry is a wildcard for the Firefox product line, and the vendor advisories (mfsa2026-97, mfsa2026-100, mfsa2026-101, mfsa2026-103) plus Bugzilla 2066321 document the fix set.
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
Sources disagree (Low–Critical)AV:N/AC:L/PR:N/UI:R/S:C/C:H/I:H/A:H
Matches Mozilla's vector: remote web content (AV:N), no privileges but victim must load a page (UI:R), and a security-boundary bypass yields scope change with high CIA when chained (S:C/C:H/I:H/A:H).
vuln.today treats the vendor’s rating as authoritative. A higher third-party CVSS (e.g. CISA-ADP) is shown for transparency but does not drive the headline severity.
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Mitigation bypass in the DOM: Security component. This vulnerability was fixed in Firefox ESR 153.4 and Firefox 157.
Executive ViewAI
Mozilla Firefox versions prior to 157 and Firefox ESR versions prior to 153.4 contain a critical security bypass that, if successfully exploited, could allow attackers to circumvent browser protections and potentially compromise sensitive data. While the vulnerability requires user interaction and chaining with another flaw for full impact, its critical severity rating and lack of a vendor patch necessitate immediate attention to assess exposure and implement interim mitigations. Leadership should prioritize monitoring and preparedness over panic, as current threat intelligence indicates no active exploitation.
No vendor patch is available. Interim mitigations include restricting use of affected Firefox versions for untrusted web content, enabling enhanced security settings within Firefox, and deploying browser isolation or alternative browsers for critical tasks. Monitor for indicators of exploitation.
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
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-88807
GHSA-wx3p-84r9-jc7f
NVD
CVE.org
EPSS
Vulnrichment
VulDB
Exploit-DB