dbcve.org
FirefoxWeb browser · Mozilla

CVE-2026-8094

CRITICAL · 9.8 CVSS v3.1 Developing Published 2026-05-07
Fix available
A fix is available. Upgrade to 140.10.2 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
Other issue in the WebRTC component. This vulnerability was fixed in Firefox ESR 140.10.2 and Thunderbird 140.10.2.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · low confidence

A critical vulnerability exists in the WebRTC component of Firefox and Thunderbird. The specific nature is described as an 'other issue' but given the 9.8 CVSS critical severity, it likely allows remote code execution or severe memory corruption. The issue was addressed in Firefox ESR 140.10.2 and Thunderbird 140.10.2.

MitigationApply the vendor-supplied updates by upgrading to Firefox ESR 140.10.2 or Thunderbird 140.10.2 to remediate this critical WebRTC vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
FirefoxWeb browser
Affected:< 140.10.2
ThunderbirdApplication
Affected:< 140.10.2

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Firefox version
    Run 'firefox --version' from command line, or open Firefox and go to Help > About Firefox to view the version number
    Affected if Version is displayed as less than 140.10.2 (e.g., 140.10.1, 140.9, etc.)
  2. Check installed Thunderbird version
    Run 'thunderbird --version' from command line, or open Thunderbird and go to Help > About Thunderbird to view the version number
    Affected if Version is displayed as less than 140.10.2 (e.g., 140.10.1, 140.9, etc.)
  3. Verify WebRTC component status
    In Firefox: go to about:config and search for 'media.peerconnection.enabled' - in Thunderbird: go to Preferences > Advanced > Config Editor and search for the same setting
    Affected if The preference 'media.peerconnection.enabled' is set to true (WebRTC is enabled)

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to 140.10.2 or later
Fixed in 140.10.2
Interim mitigation

Apply the vendor-supplied updates by upgrading to Firefox ESR 140.10.2 or Thunderbird 140.10.2 to remediate this critical WebRTC vulnerability.

Recommended fix High confidence

Firefox ESR 140.10.2 and Thunderbird 140.10.2

  1. Check current Firefox version by navigating to Help > About Firefox
  2. Check current Thunderbird version by navigating to Help > About Thunderbird
  3. For Firefox: Download Firefox ESR 140.10.2 from the official Mozilla website (www.mozilla.org)
  4. For Thunderbird: Download Thunderbird 140.10.2 from the official Mozilla website (www.mozilla.org)
  5. Close all instances of Firefox or Thunderbird
  6. Run the installer for the downloaded version
  7. Follow the installation wizard prompts to complete the update
  8. Restart the application and verify the version shows 140.10.2
Caveat Standard Mozilla release notes should be reviewed for any add-on compatibility or feature changes

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation2.0 h
  • Testing2.0 h
  • Review / QA1.0 h
6.0 hours of engineering $1,040
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,664.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-8094 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-8094 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data