Skip to main content

Mozilla Firefox CVE-2026-109771

| EUVDEUVD-2026-98531 MEDIUM
Information Exposure (CWE-200)
2026-10-13 mozilla GHSA-qhc6-j47q-3hvp
4.3
CVSS 3.1 · Vendor: mozilla
View

Attack ChainAIDerived

Hypothetical attack flow derived from CVE metadata – not a confirmed exploit chain

  1. Access
    Lure victim to malicious page
  2. Exploit
    Initiate WebRTC networking session
  3. Execution
    Trigger information disclosure flaw
  4. Impact
    Exfiltrate 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.

This Month Plan within 30 days. Why: MEDIUM severity (CVSS 4.0-6.9).
No patch listed yet 0.2% exploitation probability (EPSS)

Get an e-mail when this CVE is exploited, patched or re-scored. Free account.

Alert me

AnalysisAIv1 – 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

Vendor (mozilla) PRIMARY 4.3 MEDIUM
AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
vuln.today AI 4.3 MEDIUM

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.

3.1 AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:N/A:N
4.0 AV:N/AC:L/AT:N/PR:N/UI:P/VC:L/VI:N/VA:N/SC:N/SI:N/SA:N

Primary rating from Vendor (mozilla).

CVSS VectorVendor: mozilla

Attack Vector
Network
Attack Complexity
Low
Privileges Required
None
User Interaction
Required
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None

Lifecycle Timeline

3
CVSS changed
Oct 13, 2026 - 15:37 NVD
4.3 (MEDIUM)
CVE Published
Oct 13, 2026 - 12:29 cve.org
MEDIUM 4.3
CVE Published
Oct 13, 2026 - 12:29 cve.org
UNKNOWN (no severity yet)

DescriptionCVE.org

Information disclosure in the WebRTC: Networking component. This vulnerability was fixed in Firefox 158.

Threat Intelligence Overview

EPSS Score
0.2%
Top 90% exploitable
Prevalence
Ubiquitous
Firefox is one of the most widely deployed desktop web browsers
Data Quality
4 sources
Confidence: Medium

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.

SignalValue
Severity MEDIUM
CISA KEV No
Public POC No
EPSS 0.2%
Patch available No
Active threat No
Deciding rule
MEDIUM severity (CVSS 4.0-6.9)
What every action level means
Emergency Immediate action required. Criteria: CRITICAL + in CISA KEV (actively exploited) without patch, OR CRITICAL + EPSS > 30% without patch, OR CRITICAL + active threat signals without patch.
Act Now Prioritize within 24-48h. Criteria: in KEV with patch available, OR CRITICAL + public POC, OR HIGH + EPSS > 10%, OR CRITICAL + active threat, OR any CRITICAL severity.
This Week Schedule remediation this week. Criteria: HIGH severity (CVSS 7.0-8.9). Patch within normal change window.
This Month Plan within 30 days. Criteria: MEDIUM severity (CVSS 4.0-6.9), lower exploitation probability. Include in regular patch cycle.
Monitor Track and reassess. Criteria: LOW severity (CVSS 0.1-3.9), minimal exploitation risk. No immediate action needed.

SSVC AssessmentENISA

SSVC Decision· derived
Scheduled
Exploitation
None
System Exposure· derived
Open
Automatable
No
Human Impact· derived
Medium
Technical Impact
Partial

Priority Score

22
Low Medium High Critical
KEV: 0
EPSS: 0
CVSS: +22
PoC: 0
Weaponized: 0
Threat intel: 0
Gov advisory: 0

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

cpe:2.3:a:mozilla:firefox:*:*:*:*:*:*:*:*
CVE-2013-0758 CRITICAL POC
9.3 Jan 13

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

CVE-2013-0753 CRITICAL POC
9.3 Jan 13

Use-after-free vulnerability in the serializeToStream implementation in the XMLSerializer component in Mozilla Firefox b

CVE-2012-3993 CRITICAL POC
9.3 Oct 10

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 16.0, Firefox ESR 10.x before 10.0.8, Thunderbi

CVE-2013-1710 CRITICAL POC
10.0 Aug 07

The crypto.generateCRMFRequest function in Mozilla Firefox before 23.0, Firefox ESR 17.x before 17.0.8, Thunderbird befo

CVE-2014-8636 HIGH POC
7.5 Jan 14

The XrayWrapper implementation in Mozilla Firefox before 35.0 and SeaMonkey before 2.32 does not properly interact with

CVE-2013-0757 CRITICAL POC
9.3 Jan 13

The Chrome Object Wrapper (COW) implementation in Mozilla Firefox before 18.0, Firefox ESR 17.x before 17.0.2, Thunderbi

CVE-2014-1510 CRITICAL POC
9.8 Mar 19

The Web IDL implementation in Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and Se

CVE-2014-1511 CRITICAL POC
9.8 Mar 19

Mozilla Firefox before 28.0, Firefox ESR 24.x before 24.4, Thunderbird before 24.4, and SeaMonkey before 2.25 allow remo

CVE-2016-1960 HIGH POC
8.8 Mar 13

Integer underflow in the nsHtml5TreeBuilder class in the HTML5 string parser in Mozilla Firefox before 45.0 and Firefox

CVE-2015-0816 MEDIUM POC
5.0 Apr 01

Mozilla Firefox before 37.0, Firefox ESR 31.x before 31.6, and Thunderbird before 31.6 do not properly restrict resource

CVE-2015-0802 MEDIUM POC
5.0 Apr 01

Mozilla Firefox before 37.0 relies on docshell type information instead of page principal information for Window.webidl

CVE-2013-2566 MEDIUM POC
5.9 Mar 15

The RC4 algorithm, as used in the TLS protocol and SSL protocol, has many single-byte biases, which makes it easier for

This site uses cookies essential for authentication and security. No tracking or analytics cookies are used. Privacy Policy