Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure user to malicious page
-
DeliveryDeliver crafted DOM animation content
-
ExploitTrigger use-after-free in Animation component
-
ExecutionRead freed heap 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 the victim to load attacker-controlled web content in a vulnerable Firefox build (prior to version 158) that exercises the DOM Animation component - consistent with the CVSS UI:R requirement. No authentication is required (PR:N, so unauthenticated), and no special non-default configuration is indicated; standard web browsing with JavaScript/animation rendering enabled is sufficient. The limiting factor is the mandatory user interaction: the attack cannot succeed without the user actively visiting or rendering malicious content, which prevents automated mass exploitation (SSVC Automatable=no). Impact is limited to partial confidentiality/integrity (information disclosure from freed memory) with no demonstrated availability impact. |
| Impact | This is a moderate-severity memory-safety bug (CVSS 5.4) whose real-world priority is low-to-moderate, and multiple independent signals agree on that. CVSS shows a network vector with low complexity and no privileges (AV:N/AC:L/PR:N) but critically requires user interaction (UI:R) - the victim must load attacker-controlled content in Firefox. CISA's SSVC framework reinforces the lower urgency: Exploitation=none (no observed exploitation), Automatable=no (cannot be mass-scripted, consistent with the UI:R requirement), and Technical Impact=partial (matching the C:L/I:L/A:N partial-impact profile). There is no CISA KEV listing and no public proof-of-concept referenced, so there is no evidence of active exploitation or available exploit code. The impact is bounded: the Use-After-Free (CWE-416) is tagged Information Disclosure, suggesting out-of-bounds memory read rather than reliable remote code execution, and the A:N rating indicates no demonstrated crash/DoS impact in the scoring. No signals conflict here - every source (CVSS, SSVC, absence of KEV/POC) points to a browser memory bug that is a routine patch-and-move-on item rather than an emergency. The main caveat is inherent to UAF bugs: memory-corruption primitives can sometimes be escalated beyond the vendor's initial C:L/I:L scoring if chained with other issues, so the C:L/I:L rating may understate worst-case potential. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted DOM Animation operations and lures a Firefox user (pre-158) to visit it, for example via a phishing link or a malicious ad. When the page triggers the use-after-free in the Animation component, the attacker can read fragments of freed heap memory, potentially leaking sensitive in-process data. No public exploit code is known, and successful exploitation depends on the victim actively loading the attacker's content. |
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 Animation component allows remote attackers to corrupt memory by getting a victim to render attacker-controlled web content in a browser build prior to Firefox 158. The flaw is unauthenticated (PR:N) but requires user interaction (UI:R), since the victim must visit or render the crafted page and let it exercise animation handling; there is no public exploit identified at time of analysis and CISA's SSVC assessment records Exploitation=none with Automatable=no, so mass or automated exploitation is not expected. Impact is capped at partial confidentiality and integrity loss (CVSS 5.4, C:L/I:L/A:N), typically leaking data from freed memory or corrupting it, rather than a guaranteed full compromise.
RemediationAI
Vendor-released patch: Firefox 158 - upgrade to that version or later via the built-in update mechanism or the release downloads at https://www.mozilla.org/security/advisories/mfsa2026-106/, and verify the applied version in about:support, since the advisory is the authoritative fix reference alongside Bugzilla 2028727. If an ESR or managed deployment cannot move to 158 immediately, the exposure is driven entirely by rendering untrusted web content, so the practical short-term controls are enterprise policy to restrict high-risk browsing to sites needed for work, blocking or heavily filtering untrusted/unknown sites at the network layer, and ensuring the browser is not exempted from update enforcement - all of these reduce attack surface but have real usability costs and do not remove the bug. Disabling JavaScript or the Web Animations/CSS animation machinery is not a documented mitigation and would break most modern sites, and there is no configuration flag published for this defect, so treating the update to Firefox 158 as the only complete fix is the honest position; note that while this is a memory-safety issue, no active exploitation is reported (SSVC Exploitation=none), so patch on a normal cadence rather than treating it as an emergency.
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 affected code is the DOM: Animation component of the Gecko engine, which implements the Web Animations API and the DOM-facing machinery that drives CSS animations and transitions, including timeline objects, keyframe/effect handling, and the animation lifecycle (create, play, cancel, finish) exposed to page script. The root-cause class is CWE-416, Use After Free: an object (an animation-related DOM wrapper and its underlying engine object) is released while a reference to it remains reachable, so subsequent access operates on freed memory. That class of bug produces memory corruption and information disclosure, and in a browser engine it sits directly on the JS-to-DOM boundary where page-controlled input and object lifetimes interact. CPE data identifies the affected package as cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* - every Firefox release before 158. This was reported by Mozilla and tracked as Bugzilla 2028727, with the fix shipped in the mfsa2026-106 advisory, and it also carries ENISA EUVD ID EUVD-2026-98497.
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
Remote web content exploitation gives AV:N/AC:L/PR:N, but the victim must load malicious content so UI:R; the info-disclosure UAF yields partial C:L/I:L with no availability impact.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Use-after-free in the DOM: Animation 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
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-98497
GHSA-q7wm-wcvx-wfx8
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB