Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
ExploitDeliver crafted Site Reports content
-
ExecutionTrigger uncontrolled resource consumption
-
ImpactBrowser hang or crash (DoS)
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V2 - Validation and Business Logic Resource consumption limits
MITRE ATT&CK
1 technique across 1 tactic: Impact The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires the victim to use Mozilla Firefox (versions prior to 158) and to actively load attacker-controlled content processed by the Site Reports component - the UI:R metric confirms user interaction (navigating to or opening malicious content) is mandatory, which limits mass automated exploitation (SSVC Automatable: no). No authentication is required (PR:N) and no special non-default configuration is indicated in the description. The impact is confined to availability of the client browser (A:H, C:N/I:N) with no scope change (S:U), so no persistence, data compromise, or lateral movement results; the realistic worst case is a browser crash or hang for the targeted user. |
| Impact | This is a medium-severity denial-of-service issue (CVSS 6.5) in Firefox's Site Reports component, mapped to CWE-400 (uncontrolled resource consumption). The CVSS vector CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H indicates a network-reachable, low-complexity, unauthenticated attack that requires user interaction and impacts only availability (C:N/I:N) - consistent with a browser crash/hang rather than code execution or data exposure. Multiple risk signals align toward LOW real-world priority: CISA SSVC assesses Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial', and there is no public exploit identified at time of analysis (not in CISA KEV, no POC referenced). No EPSS score was provided in the input, so probabilistic exploitation likelihood cannot be quantified - this is a data gap. The signals are internally consistent (no exploitation observed, availability-only impact, interaction-gated), so this reads as a genuine but low-urgency vulnerability appropriately resolved through routine patching rather than an emergency. The primary mitigating factor is that impact is limited to availability of the client browser process, not the underlying system or other users. |
| Exploit ScenarioDerived | An attacker hosts or injects malicious web content that, when a victim's Firefox browser renders it via the Site Reports component, triggers uncontrolled resource consumption causing the browser to hang or crash (denial of service). The attack requires the user to interact by visiting the attacker-controlled page (UI:R), and no authentication is needed. No public exploit code was identified at time of analysis. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Denial of service in Mozilla Firefox allows a remote attacker to crash or hang the browser by getting a victim to load crafted content processed by the Site Reports component; versions prior to Firefox 158 are affected. Exploitation requires user interaction (the victim must navigate to or open the attacker-controlled content, per the UI:R metric) and no authentication is required (PR:N), but the SSVC assessment marks the issue as non-automatable, and no public exploit code or active exploitation has been identified at time of analysis. Impact is limited to client-side availability (A:H with no confidentiality or integrity loss and no scope change), so the realistic worst case is a crashed or unresponsive browser session for the targeted user.
RemediationAI
Vendor-released patch: Firefox 158 - upgrading to Firefox 158 or later is the definitive fix, distributed through Firefox's built-in update mechanism, the Mozilla download channel, or the equivalent package in your Linux distribution's repositories. Because there is no vendor-released mitigation other than the version upgrade and no confirmation that the affected component can be toggled off in a supported way, the practical interim controls are exposure-reduction measures with clear trade-offs: keep Firefox on the current release channel and enable automatic updates so the fix is applied as soon as it is offered; restrict browsing of untrusted or attacker-supplied content (links, attachments, embedded pages) to a sandboxed or disposable browser profile or virtual machine, accepting the operational overhead and degraded user experience this imposes; and treat browser crashes or hangs as availability events rather than compromise indicators, since the assessed impact is limited to availability (C:N/I:N, S:U). Verify the applied version after updating, and consult Mozilla's advisory MFSa2026-106 (https://www.mozilla.org/security/advisories/mfsa2026-106/) and the Bugzilla entry (https://bugzilla.mozilla.org/show_bug.cgi?id=2011368) for the authoritative fix confirmation.
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 an uncontrolled resource consumption issue (CWE-400) in Firefox's Site Reports component, a browser-side feature that processes content associated with a visited site. Rather than a memory-corruption or code-execution flaw, the defect lets crafted input drive the component into excessive resource consumption, degrading or halting the browser process - consistent with the assessed CVSS:3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H, where only Availability is impacted at High severity, Scope is Unchanged, and Confidentiality and Integrity are Not affected. The affected product set is captured by CPE cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*, i.e. the Mozilla Firefox browser channel built and distributed by Mozilla; per the vendor advisory the issue is resolved in Firefox 158. Root cause class (CWE-400) implies missing or insufficient limits on the resources consumed while handling Site Reports input, so the fix is expected to be a bound/limit on that processing path rather than a change to the browser's security model.
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:N/I:N/A:H
Remote web content with no auth (AV:N/PR:N) but requires the user to load the page (UI:R); availability-only browser DoS (A:H, C:N/I:N), no scope change.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Denial-of-service in the Site Reports 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
Denial of Service attacks render applications or systems unavailable by overwhelming resources or triggering failure conditions.
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-98528
GHSA-cqh4-gcrp-84w4
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB