dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-46881

HIGH · 8.8 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.6 / 106.0 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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
An optimization in WebGL was incorrect in some cases, and could have led to memory corruption and a potentially exploitable crash. *Note*: This advisory was added on December 13th, 2022 after we better understood the impact of the issue. The fix was included in the original release of Firefox 106. This vulnerability affects Firefox < 106, Firefox ESR < 102.6, and Thunderbird < 102.6.

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

A flawed WebGL optimization in Firefox and Thunderbird causes memory corruption that can trigger a potentially exploitable crash. This client-side vulnerability in the graphics rendering pipeline has a CVSS of 8.8 due to network-exploitable nature, low attack complexity, and no required privileges.

MitigationUpdate affected software to Firefox 106, Firefox ESR 102.6, or Thunderbird 102.6. Apply via standard patch management or manual update.

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:< 106.0
Firefox EsrWeb browser
Affected:< 102.6
ThunderbirdApplication
Affected:< 102.6

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
Required
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/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. Identify installed Firefox or Thunderbird version
    Run 'firefox --version' or ' thunderbird --version' from command line, or open the application and go to Help > About to view the version number
    Affected if Version is below 106.0 for Firefox, below 102.6 for Firefox ESR, or below 102.6 for Thunderbird
  2. Confirm WebGL is accessible in the browser
    In Firefox address bar, type 'about:config' and search for 'webgl.disabled' preference, or visit a WebGL test site to confirm the feature is functional
    Affected if WebGL is not explicitly disabled (webgl.disabled is not set to true) and the browser renders WebGL content
  3. Check if system has any crash logs from WebGL activity
    In Firefox, go to 'about:crashes' to view recent crash reports; look for crashes occurring during graphics or WebGL rendering
    Affected if There are recent crash reports tied to WebGL or graphics rendering processes on unpatched versions

A user is affected if they are running an unpatched Firefox (below 106.0), Firefox ESR (below 102.6), or Thunderbird (below 102.6) with WebGL enabled and actively using WebGL content.

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 102.6 / 106.0 or later
Fixed in 102.6106.0
Interim mitigation

Update affected software to Firefox 106, Firefox ESR 102.6, or Thunderbird 102.6. Apply via standard patch management or manual update.

Recommended fix High confidence

Firefox 106.0 / Firefox ESR 102.6 / Thunderbird 102.6 (or later)

  1. Identify the installed product (Firefox, Firefox ESR, or Thunderbird) and current version
  2. For Firefox: upgrade to version 106.0 or later
  3. For Firefox ESR: upgrade to version 102.6 or later
  4. For Thunderbird: upgrade to version 102.6 or later
  5. Restart the application after upgrading
  6. Verify the upgrade was successful by checking the application version
Caveat Standard version upgrades typically have no breaking changes for end users; however, ensure compatibility with any site-specific plugins or extensions

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

Fix this in Firefox Scoped from the published advisory
  • Consultation2.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $910
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,456.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2022-46881 — 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-2022-46881 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