Attack ChainAIDerived
Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain
-
AccessLure victim to malicious page
-
ExploitInitiate WebRTC networking session
-
ExecutionTrigger information disclosure flaw
-
ImpactExfiltrate leaked data
Vulnerability Assessment
| Weakness |
CWE
OWASP Top 10:2025
A01:2025 - Broken Access Control
ASVS 5.0
V14 - Data Protection Data exposure prevention
MITRE ATT&CK
2 techniques across 2 tactics: Collection, Discovery 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 a vulnerable Firefox build prior to version 158 and to interact with attacker-controlled web content that drives the WebRTC: Networking component (CVSS UI:R), meaning WebRTC must be reachable/active in the browsing session. No authentication is required of the attacker (PR:N), but the mandatory user interaction and the limitation of impact to a partial confidentiality leak (C:L/I:N/A:N) substantially constrain realistic risk; upgrading to Firefox 158 fully removes the condition. |
| Impact | This is a genuinely low-priority issue despite the 'Medium' CVSS 4.3 rating. The CVSS vector (AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N) describes a network-reachable, unauthenticated flaw that nonetheless requires user interaction (UI:R) and yields only low-magnitude confidentiality impact with no integrity or availability effect - consistent with CWE-200 information disclosure in the WebRTC networking stack. All exploitation signals point the same direction and reinforce low risk: CISA SSVC lists Exploitation as 'none', Automatable 'no', and Technical Impact only 'partial'. No CISA KEV listing is present and no EPSS score was supplied in the input, so widespread-exploitation probability cannot be quantified but nothing suggests it. No public exploit identified at time of analysis. There is no conflict between the signals here - the modest CVSS, the SSVC 'none/no/partial' triad, and the absence of KEV/POC all agree. The only caveat is that EPSS data is missing from the input, so the exploitation-probability dimension is unverified rather than confirmed-low. |
| Exploit ScenarioDerived | An attacker hosts a malicious web page that establishes or manipulates a WebRTC networking session; when a victim using a pre-158 Firefox build visits the page and interacts with it (UI:R), the flaw leaks a limited amount of sensitive information such as internal network or memory-resident data. No public exploit is identified and impact is confined to partial confidentiality disclosure, with no code execution or data tampering. |
Get an e-mail when this CVE is exploited, patched or re-scored. Free account.
Alert meAnalysisAIv1 – Oct 13, 2026
Information disclosure in the WebRTC: Networking component of Mozilla Firefox lets attacker-controlled web content coax limited data out of the browser, affecting all builds prior to Firefox 158. Exploitation is remote and requires no attacker credentials, but it mandates user interaction (CVSS UI:R) and yields only a partial confidentiality leak (C:L with no integrity or availability impact), which keeps realistic risk low despite the Medium 4.3 score. There is no public exploit identified at time of analysis, CISA SSVC records exploitation as 'none' and automatable as 'no', and upgrading to Firefox 158 fully removes the condition.
RemediationAI
The primary and complete fix is to upgrade to Firefox 158, the release in which Mozilla addressed this issue (vendor-released patch: Firefox 158), available through the normal update channel - desktop clients should be force-updated via Help > About Firefox, and enterprises should push the 158 build through their managed software deployment or Firefox ESR-equivalent policy tooling; details are in Mozilla's advisory https://www.mozilla.org/security/advisories/mfsa2026-106/ and the source bug https://bugzilla.mozilla.org/show_bug.cgi?id=2059658. Because the flaw lives in the WebRTC networking path, an interim compensating control is to disable WebRTC until patching is possible by setting media.peerconnection.enabled to false in about:config, or by enforcing the same setting through an enterprise policies.json - the trade-off is that this breaks all WebRTC-dependent services such as browser-based video conferencing, screen sharing and peer-to-peer data channels, so it should be scoped only to high-risk user populations. Additional hardening that reduces exposure without disabling WebRTC includes restricting the ability to reach untrusted web content from the affected profile and ensuring WebRTC-related permissions (camera, microphone, screen capture) are denied by default, since the issue requires user interaction to trigger; neither mitigation is a substitute for the 158 upgrade, which is the only action that removes the vulnerability outright.
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 sits in Firefox's WebRTC networking stack, the subsystem that handles ICE/STUN/TURN negotiation, peer connection setup and the transport of real-time media and data channels. Classified under CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor), the flaw is a confidentiality-only weakness: the networking layer can be driven by attacker-supplied page content to disclose data it should not reveal, without granting code execution, data modification or denial of service (I:N/A:N). The CVSS 3.1 vector AV:N/AC:L/PR:N/UI:R/S:U/C:L confirms the attack is network-delivered and trivially automatable in terms of complexity, but it is gated by a mandatory human action and confined to a single security scope with low confidentiality impact. Mozilla's own SSVC evaluation (Exploitation: none, Automatable: no, Technical Impact: partial) aligns with this constrained profile, indicating the bug is not being leveraged opportunistically and does not lend itself to mass exploitation. The WebRTC component must be active and reachable in the victim's browsing session for the interaction to reach the vulnerable code path, which narrows the practical attack surface further.
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:N/A:N
Network-reachable via malicious web content (AV:N) but requires victim interaction (UI:R) and no privileges (PR:N); impact limited to minor information disclosure, so C:L and I/A:N.
Primary rating from Vendor (mozilla).
CVSS VectorVendor: mozilla
Lifecycle Timeline
3DescriptionCVE.org
Information disclosure in the WebRTC: Networking 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
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-98531
GHSA-qhc6-j47q-3hvp
NVD
CVE.org
EPSS
Vulnrichment
Exploit-DB