Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
DeliveryDeliver crafted WebAssembly/JS payload
-
ExploitTrigger use-after-free in WASM engine
-
ExecutionReuse freed memory object
-
ImpactLeak in-process memory / corrupt state
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 WebAssembly feature of Firefox's JavaScript engine to process attacker-supplied WASM/JS content - i.e., the victim must open or render a malicious web page or document in an unpatched Firefox prior to version 158 (UI:R in the vector). No authentication is needed (PR:N) and the attack is network-delivered (AV:N) against default configurations, since WebAssembly is enabled by default. The principal LIMITING factor is the mandatory user interaction (visiting/loading attacker content); there is no privilege requirement and no special non-default configuration is needed. Impact is bounded - low confidentiality and integrity effect, no availability impact - consistent with a constrained memory-disclosure/corruption primitive rather than full system compromise. |
| Impact | This is a medium-severity (CVSS 5.4) use-after-free (CWE-416) in Firefox's JavaScript WebAssembly component. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:N) indicates a network-reachable, low-complexity, unauthenticated flaw that requires user interaction (victim must load attacker-controlled content) with only low confidentiality and integrity impact and no availability impact. The multiple signals are mutually consistent and all point AWAY from urgent priority: SSVC reports Exploitation=none, Automatable=no, Technical Impact=partial, which aligns with the low CVSS impact metrics and the requirement for user interaction. There is no CISA KEV listing and no EPSS score was provided in the input, so exploitation probability could not be quantified; no public exploit code was referenced. The 'Memory Corruption' tag might suggest code-execution potential typical of UAF bugs, but the vendor-assigned impact (C:L/I:L/A:N, tagged 'Information Disclosure') and SSVC 'partial' technical impact suggest this was assessed as a limited info-leak/memory-disclosure primitive rather than reliable remote code execution. Net assessment: a real but non-urgent browser memory-safety bug - patch via normal update cadence rather than emergency response. NOTE: EPSS data is absent from the input, so widespread-exploitation likelihood cannot be confirmed either way. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page containing crafted JavaScript/WebAssembly that triggers the use-after-free in Firefox's WASM engine; when a victim using an unpatched Firefox (before 158) visits the page, the freed-then-reused memory is leveraged to disclose sensitive in-process memory contents and/or corrupt limited integrity-relevant state. No authentication is required, but the victim must actively load the attacker's content (UI:R). No public proof-of-concept exploit was identified in the provided intelligence. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
A use-after-free (CWE-416) in Firefox's JavaScript WebAssembly component lets remote, unauthenticated attackers trigger memory corruption with low confidentiality and integrity impact (CVSS 5.4) when a victim loads attacker-supplied WASM/JS content in any build prior to Firefox 158. Exploitation is constrained by a mandatory user-interaction requirement - the target must open or render a malicious page or document - and by the absence of any availability impact, indicating a bounded disclosure/corruption primitive rather than full system compromise. CISA's SSVC evaluation rates exploitation as none and automatable as no, and no public exploit code has been identified at time of analysis; Mozilla fixed the flaw in Firefox 158.
RemediationAI
Vendor-released patch: Firefox 158 - upgrade to Firefox 158 or later through the normal update channel, and verify the applied build in about:firefox/about:support rather than relying on auto-update alone; the authoritative details are in Mozilla's MFSA2026-106 advisory (https://www.mozilla.org/security/advisories/mfsa2026-106/) with the engineering fix recorded in Bugzilla 2067169 (https://bugzilla.mozilla.org/show_bug.cgi?id=2067169). If immediate upgrade is impossible, the most direct compensating control is to disable WebAssembly in the affected Firefox builds by toggling the wasm preference in about:config (javascript.options.wasm) to false and pushing the same via enterprise policy - the trade-off is concrete and non-trivial: any site that depends on WASM, including many browser-based productivity apps, games, video-conferencing clients, and streaming tools, will break or degrade. Restricting users to a curated allowlist of trusted sites through proxy/DNS filtering reduces exposure because the attack requires the victim to load attacker-supplied content, but it does not eliminate risk for users who browse freely, and it adds an operational maintenance burden. Because exploitation is neither automatable per SSVC nor associated with active exploitation, there is no evidence-driven need for emergency network-level blocking beyond normal patch cadence; prioritize the 158 update, and treat pre-158 Firefox as an unpatched browser for vulnerability-management reporting purposes.
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 component is Firefox's JavaScript engine (SpiderMonkey) WebAssembly subsystem, the layer that compiles and executes the sandboxed WASM binary format delivered alongside JavaScript in web content. CWE-416 (Use-After-Free) means a heap object remains referenced by a dangling pointer after it has been freed, so a subsequent dereference can read or write memory that has been reallocated - the tag set (Memory Corruption, Use After Free, Information Disclosure) is consistent with that root-cause class. WebAssembly is enabled by default in shipping Firefox builds and requires no non-default configuration, so the only practical barrier is the UI:R requirement that the victim fetch and render attacker-controlled WASM/JS content; the unauthenticated, network-delivered vector (AV:N/PR:N/AC:L) reflects that any web page or document capable of embedding script is a delivery vehicle. The bounded scoring (C:L/I:L, A:N per the authoritative assessment) and the SSVC technical-impact rating of "partial" indicate a constrained primitive rather than a remotely reachable path to arbitrary code execution at the assessed level, though use-after-free bugs in script engines are historically the class that memory-safety mitigations exist to contain. The CPE entry cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* covers the pre-158 Firefox release channel generally, with no platform restriction implied.
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
Network-delivered WASM content triggers the bug (AV:N/AC:L), no auth needed (PR:N) but victim must load the page (UI:R); vendor-assessed limited info-leak/corruption gives C:L/I:L/A:N, scope unchanged.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Use-after-free in the JavaScript: WebAssembly 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-98510
GHSA-pmrg-jx35-2qp3
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB