Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
ExploitTrigger timed XPCOM operations
-
ExecutionWin race condition window
-
ImpactDisclose limited in-process data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A06:2025 - Insecure Design
ASVS 5.0
V15 - Secure Coding and Architecture Concurrency control, locking
MITRE ATT&CK
1 technique across 1 tactic: 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 visit or interact with attacker-controlled web content (UI:R) rendered by a vulnerable Firefox build, and the attacker must successfully win a non-deterministic timing race in the XPCOM component (reflected in AC:H), which cannot be triggered reliably on demand. No authentication is required (PR:N). Exploitation is limited to versions prior to Firefox 158 and Firefox ESR 153.5; updated builds are not affected. Impact is constrained to limited information disclosure (C:L/I:L, A:N), with no scope change (S:U), so even on success the attacker gains only small, partial access rather than code execution or full compromise. |
| Impact | This is a genuinely low-priority issue by most signals, and they are internally consistent. The CVSS 3.1 base score of 4.2 (Medium) reflects a hard-to-win condition: AV:N but AC:H (winning a race window is non-deterministic), UI:R (victim must perform some browsing action), and only partial, unchanged-scope impact (C:L/I:L/A:N). EPSS reinforces this - 0.19% probability at the 8th percentile indicates very low expected exploitation volume. The vulnerability is NOT on CISA KEV and no public POC is referenced, so exploitation status is 'no public exploit identified at time of analysis.' There is no SSVC decision data provided. The only mild tension is between AV:N (network) and the practical reality of exploiting a XPCOM race condition, which requires precise timing against a browser process; the AC:H metric already captures that difficulty, so the signals do not actually conflict. Overall this is a legitimately low-urgency, low-real-risk flaw that should be remediated via normal Firefox update cadence rather than emergency patching. |
| Exploit ScenarioDerived | An attacker hosts or compromises a web page and lures a Firefox user to visit it (UI:R). The page performs timed operations that attempt to trigger a race condition in the XPCOM component, and on a successful race the attacker gains limited read access to small amounts of in-process data (C:L). No public exploit code is referenced, and the high attack complexity (AC:H) means success is probabilistic rather than reliable. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 15, 2026
A non-deterministic timing race in Mozilla Firefox's XPCOM component can be won by attacker-controlled web content to yield limited information disclosure and a small integrity impact inside the browser, affecting Firefox builds prior to 158 and Firefox ESR builds prior to 153.5. Exploitation requires the victim to load or interact with attacker-supplied content (UI:R) and to hit a narrow, hard-to-reproduce race window (AC:H); no credentials are required (PR:N), and impact stays at low confidentiality and integrity with no scope change and no availability effect. Risk is low across every signal available: EPSS 0.19% (8th percentile), no CISA KEV listing, and no public exploit identified at time of analysis, while vendor-released patches (Firefox 158 and Firefox ESR 153.5) are already available.
RemediationAI
Apply the vendor-released patches by upgrading to Firefox 158 or, on the extended-support train, Firefox ESR 153.5; both versions are the authoritative fixes identified in Mozilla advisories mfsa2026-106, mfsa2026-108, mfsa2026-109 and mfsa2026-110, with technical detail in Bugzilla 2069395. Track the fixes via https://www.mozilla.org/security/advisories/mfsa2026-106/ and https://www.mozilla.org/security/advisories/mfsa2026-108/ (and the companion mfsa2026-109/mfsa2026-110 pages), and confirm the running build in about:support or via the enterprise ESR update channel, since the reported CPE uses a version wildcard and only the fixed release numbers distinguish patched from unpatched systems. No configuration-level fix is documented, so any compensating control is a stopgap with real trade-offs: enforcing rapid automatic updates through enterprise policy (DisableAppUpdate disabled, AppUpdateURL pinned to your own mirror) shrinks the exposure window but requires a managed update pipeline; restricting general browsing to trusted internal content or routing untrusted sites through an isolated/remote-rendered browser reduces the chance of meeting the UI:R precondition but degrades usability and does not protect users who must browse the open web; disabling JavaScript wholesale would remove most scripted paths to the race but breaks the majority of modern sites and is not practical outside narrow kiosk deployments. Given the low EPSS score (0.19%, 8th percentile), no CISA KEV listing, and no public exploit identified, patch on the normal maintenance cycle rather than through an emergency change process.
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
XPCOM is Mozilla's cross-platform component object model, the interface layer through which Gecko and browser JavaScript access native, scriptable components such as DOM, networking, and storage services. The flaw is a classic CWE-362 race condition: a shared XPCOM-backed resource is accessed or mutated concurrently without adequate synchronization, leaving a narrow interleaving window in which attacker-influenced script execution can observe or alter state it should not reach. The high attack complexity (AC:H) reflects that the attacker must win a non-deterministic timing race that cannot be triggered reliably on demand, and the required user interaction (UI:R) reflects that the malicious code must first be rendered as web content by the vulnerable browser. Because the assessed vector caps impact at C:L and I:L with A:N and S:U, the primitive is expected to produce only partial, piecemeal exposure or minor state corruption rather than memory corruption, sandbox escape, or code execution; the CPE string cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:* is a version wildcard, so the actual boundary between vulnerable and fixed builds is defined solely by the fixed releases Firefox 158 and Firefox ESR 153.5 cited in the Mozilla advisories.
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:H/PR:N/UI:R/S:U/C:L/I:L/A:N
Web-delivered so AV:N and UI:R; a race condition is non-deterministic giving AC:H; no auth needed (PR:N); only limited disclosure/integrity impact, no availability effect.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Race condition in the XPCOM component. This vulnerability was fixed in Firefox 158 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
Information disclosure occurs when an application unintentionally exposes sensitive data that aids attackers in reconnaissance or directly compromises security.
Race conditions occur when multiple concurrent requests exploit the brief time gap between checking a condition and acting upon it (TOCTOU - Time of Check, Time of Use).
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-98536
GHSA-xmv6-f4v8-qgcx
NVD
CVE.org
EPSS
Exploit-DB