Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious web page
-
DeliveryServe crafted DOM/HTML content
-
ExploitTrigger use-after-free in DOM Core & HTML
-
ExecutionReuse freed object to read stale memory
-
ImpactDisclose sensitive in-process data
Vulnerability Assessment
| Weakness |
CWE
ASVS 5.0
V15 - Secure Coding and Architecture Memory lifecycle management
MITRE ATT&CK
2 techniques across 2 tactics: Execution, Privilege Escalation The technique list with ATT&CK links and the kill-chain view is part of the Basic plan and up. |
| Exploitation Conditions | Exploitation requires a user to actively load attacker-controlled web content in Firefox that exercises the vulnerable DOM: Core & HTML code path triggering the use-after-free (UI:R). No authentication or prior privileges are needed (PR:N) and the attack is network-delivered (AV:N), so any default Firefox installation that browses to a malicious or compromised page is in scope - no non-default feature or configuration setting is named in the advisory. The principal LIMITING factors are the mandatory user interaction (the victim must visit the page), the impact ceiling (partial confidentiality/integrity only, no availability per A:N), and the patch being already available: upgrading to Firefox 158, Firefox ESR 115.43, or Firefox ESR 153.5 fully remediates it. |
| Impact | This is a moderate-severity, low-real-world-priority issue despite being a memory-corruption class (CWE-416 use-after-free). The CVSS 3.1 base score of 5.4 (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) describes a network-reachable flaw that an unauthenticated attacker can trigger but that REQUIRES user interaction (UI:R) and yields only partial confidentiality and integrity impact with no availability impact - consistent with an information-disclosure-style memory leak rather than reliable code execution. All signals agree this is not an urgent priority: CISA SSVC rates Exploitation as 'none', Automatable as 'no', and Technical Impact as only 'partial', and the input provides no EPSS score, no KEV listing, and no evidence of public exploit code. There is no conflict between the CVSS network vector and the description - a user visiting a malicious web page is the natural delivery path for a browser DOM bug, which fully explains the AV:N/UI:R combination. The one note of caution is inherent to the bug class: use-after-free conditions in a browser DOM engine are historically a favored primitive for building more serious exploit chains, so the modest 'C:L/I:L/A:N' impact rating may understate worst-case potential if combined with other bugs; however, nothing in the supplied data indicates weaponization. No EPSS data was provided, so probabilistic exploitation likelihood cannot be quantified here. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted DOM/HTML content that triggers the use-after-free in Firefox's DOM Core & HTML component, then lures a victim into visiting it. When the freed object is reused, the attacker can read fragments of adjacent memory, potentially disclosing sensitive in-process data. No public exploit code was identified in the provided data, and user interaction (visiting the page) is required. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Use-after-free in Mozilla Firefox's DOM: Core & HTML component allows remote attackers to trigger memory corruption when a victim loads attacker-controlled web content, requiring user interaction (UI:R) with no authentication or prior privileges needed (PR:N). Any default Firefox installation that browses to a malicious or compromised page is in scope, but the impact ceiling is limited to partial confidentiality and integrity loss with no availability impact (C:L/I:L/A:N), and Mozilla has already shipped fixes in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5. There is no public exploit identified at time of analysis, exploitation is not automatable per SSVC (Exploitation: none, Automatable: no, Technical Impact: partial), and this is a moderate-severity, low-real-world-priority issue despite belonging to the memory-corruption class (CWE-416).
RemediationAI
Vendor-released patch: upgrade to Firefox 158, Firefox ESR 115.43, or Firefox ESR 153.5 as applicable to your release channel - this fully remediates the issue and is the only action needed, per advisories https://www.mozilla.org/security/advisories/mfsa2026-106/, https://www.mozilla.org/security/advisories/mfsa2026-107/, and https://www.mozilla.org/security/advisories/mfsa2026-108/. Given the moderate severity, non-automatable SSVC profile, and absence of identified public exploit code, emergency out-of-band deployment is not warranted, but organizations with extended-support deployments should prioritize the ESR branches (115.43 and 153.5) since those users will not receive the main-line 158 fix. If immediate upgrade is impossible, the realistic compensating control is to constrain browsing to trusted, non-attacker-controlled origins and enforce a policy that discourages visiting untrusted or compromised sites, ideally layered with renderer sandboxing and exploit-mitigation hardening; the trade-off is that this materially degrades usability and is not a reliable substitute for patching, and disabling JavaScript would break most modern sites while providing only partial mitigation since the DOM parsing path may be exercised beyond script execution. Blocking network delivery is impractical because the attack arrives through ordinary web browsing rather than a distinct service port, so patching remains the primary and preferred remedy.
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 a use-after-free (CWE-416) in Firefox's DOM: Core & HTML component - the code layer that parses and represents HTML documents and implements the core DOM interfaces exposed to web content. In a use-after-free, an object or buffer is released while a reference to it remains live; subsequent access reads or writes memory that may already have been reallocated, producing memory corruption. Because the vulnerable code path is reachable from ordinary web content rendered in the browser, a crafted or compromised page can drive the stale reference, and the affected CPE (cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*) confirms that all Firefox releases predating the fix line are candidates. The associated tags (Use After Free, Memory Corruption, Information Disclosure) align with the assessed impact ceiling of partial confidentiality and integrity loss with no availability component; the advisory names no non-default feature or configuration prerequisite, so the exposed surface is effectively the default browsing configuration, gated only by the mandatory user interaction of visiting the page.
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:L/I:L/A:N
Browser DOM bug reached by visiting a malicious page: AV:N and PR:N but UI:R; use-after-free yields partial info leak so C:L/I:L and A:N with no scope change.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Use-after-free in the DOM: Core & HTML component. This vulnerability was fixed in Firefox 158, Firefox ESR 115.43, and Firefox ESR 153.5.
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
Use-after-free vulnerabilities occur when a program continues to access memory through a pointer after that memory has been deallocated.
Memory corruption occurs when a program writes data beyond the boundaries of allocated memory regions or accesses memory in unintended ways, violating the integrity of the process's address space.
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-98643
GHSA-h2fj-2h2q-386x
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB