CVE-2026-8958
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 · uneditedInformation disclosure, sandbox escape in the Security: Process Sandboxing 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 confidenceThis is an information disclosure and sandbox escape vulnerability in Mozilla Firefox and Thunderbird's Security: Process Sandboxing component. A successful exploit could allow malicious code to break out of the browser's security sandbox and potentially access sensitive information or execute arbitrary code on the host system.
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< 140.11.0< 151.0.0< 140.11< 151.0.0CVSS 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
- Changed
- Confidentiality
- High
- Integrity
- None
- Availability
- None
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N
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 checksWork through these to decide whether this CVE applies to you.
-
Check Firefox version on WindowsOpen Firefox, click the menu (three lines) > Help > About Firefox. The version number is displayed in the window that opens.Affected if The version shown is below 140.11.0 or below 151.0.0 (for example, 140.10.x, 150.x.x, or any 139.x release)
-
Check Firefox version on macOSOpen Firefox, click the Firefox menu > About Firefox. The version number is displayed in the window.Affected if The version shown is below 140.11.0 or below 151.0.0
-
Check Firefox version on LinuxOpen a terminal and run: firefox --versionAffected if The version output is below 140.11.0 or below 151.0.0
-
Check Thunderbird version on WindowsOpen Thunderbird, click the menu (three lines) > Help > About Thunderbird. The version number is displayed.Affected if The version shown is below 140.11 or below 151.0.0
-
Check Thunderbird version on Linux/macOSOpen a terminal and run: thunderbird --versionAffected if The version output is below 140.11 or below 151.0.0
-
Verify if sandboxing is enabled (optional context)In Firefox or Thunderbird, type about:config in the address bar, search for 'sandbox', and check if security.sandbox.enabled is set to true (default state).Affected if This check confirms the vulnerable component is active - the sandbox is enabled by default in affected versions.
A user is affected if either Firefox version is below 140.11.0 or below 151.0.0, or if Thunderbird version is below 140.11 or below 151.0.0, with sandboxing enabled (default).
Generated from the published advisory. Verify against your own configuration.
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 · scoped140.11140.11.0151.0.0
Update Firefox to version 151 or later (ESR 140.11 or later), and Thunderbird to version 151 or later (140.11 or later). Alternatively, apply the latest security updates from Mozilla.
Firefox 151 or Firefox ESR 140.11; Thunderbird 151 or Thunderbird 140.11
- Check current Firefox version by navigating to about:settings or going to Menu > Help > About Firefox
- Check current Thunderbird version by navigating to Menu > Help > About Thunderbird
- For Firefox: Download Firefox 151 (or Firefox ESR 140.11 for enterprise/long-term support) from the official Mozilla website
- For Thunderbird: Download Thunderbird 151 (or Thunderbird 140.11 for enterprise/long-term support) from the official Mozilla website
- Install the downloaded version, overwriting the existing installation
- Restart the browser/application after installation completes
- Verify the version by checking about:settings (Firefox) or Menu > Help > About Thunderbird to confirm the fix is applied
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation1.0 h
- Implementation1.0 h
- Testing1.0 h
- Review / QA1.0 h
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 locallyCheck whether your project pulls in CVE-2026-8958 — 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 sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-8958 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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