FirefoxWeb browser · Mozilla

CVE-2026-8949

HIGH · 7.5 CVSS v3.1 Published 2026-05-19
Fix available
A fix is available. Upgrade to 140.11 / 140.11.0 or later.
See remediation →
84/100
Remediation priority · High
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
Integer overflow in the Widget: Win32 component. This vulnerability was fixed in Firefox 151, Firefox ESR 140.11, Thunderbird 151, and Thunderbird 140.11.

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 · moderate confidence

Integer overflow vulnerability in the Widget: Win32 component of Firefox and Thunderbird on Windows. This could allow an attacker to cause a denial of service or potentially achieve arbitrary code execution via integer overflow leading to memory corruption.

MitigationUpdate to Firefox 151 or later, Firefox ESR 140.11 or later, Thunderbird 151 or later, or Thunderbird 140.11 or later to apply the vendor patch.

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.11.0< 151.0.0
ThunderbirdApplication
Affected:< 140.11< 151.0.0

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
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/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. Confirm Windows environment
    Verify the operating system is Windows since the vulnerability specifically affects the Win32 component
    Affected if Running on Windows with Firefox or Thunderbird installed
  2. Check Firefox version on Windows
    Open Firefox, click the menu button (three horizontal lines), select Help, then About Firefox. Alternatively, run 'firefox --version' or check the executable properties of firefox.exe
    Affected if Installed Firefox version is less than 140.11.0 OR less than 151.0.0
  3. Check Thunderbird version on Windows
    Open Thunderbird, click the menu button, select Help, then About Thunderbird. Alternatively, run 'thunderbird --version' or check the executable properties of thunderbird.exe
    Affected if Installed Thunderbird version is less than 140.11 OR less than 151.0.0

A user is affected if running Firefox or Thunderbird on Windows with a version below 140.11/140.11.0 or below 151.0.0 in either the regular or ESR release tracks

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.11 / 140.11.0 / 151.0.0 or later
Fixed in 140.11140.11.0151.0.0
Interim mitigation

Update to Firefox 151 or later, Firefox ESR 140.11 or later, Thunderbird 151 or later, or Thunderbird 140.11 or later to apply the vendor patch.

Recommended fix High confidence

Firefox 151 / Firefox ESR 140.11 / Thunderbird 151 / Thunderbird 140.11

  1. 1. Check current Firefox version by clicking Help > About Firefox
  2. 2. Check current Thunderbird version by clicking Help > About Thunderbird
  3. 3. For Firefox: Click 'Check for Updates' in the About dialog or wait for automatic update notification, then install version 151 or ESR 140.11
  4. 4. For Thunderbird: Click 'Check for Updates' in the About dialog or wait for automatic update notification, then install version 151 or 140.11
  5. 5. Alternatively, download the appropriate version from https://www.mozilla.org/firefox/releases/ or https://www.mozilla.org/thunderbird/releases/
  6. 6. Restart the application after the update completes

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

Fix this in Firefox Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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

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-8949 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