dbcve.org
FirefoxWeb browser · Mozilla

CVE-2022-46882

CRITICAL · 9.8 CVSS v3.1 Published 2022-12-22
Fix available
A fix is available. Upgrade to 102.6 / 107.0 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
A use-after-free in WebGL extensions could have led to a potentially exploitable crash. This vulnerability affects Firefox < 107, 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 use-after-free vulnerability in WebGL extensions allows memory to be accessed after it has been freed, potentially leading to exploitable crashes and possible arbitrary code execution.

MitigationUpdate affected products to Firefox 107+, Firefox ESR 102.6+, or Thunderbird 102.6+ to patch the 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:< 107.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
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. Identify installed Mozilla product
    Check for Firefox, Firefox ESR, or Thunderbird by running: which firefox firefox-esr thunderbird or checking /usr/bin/ for mozilla products
    Affected if Product is Firefox, Firefox ESR, or Thunderbird (other products are not affected)
  2. Determine Firefox version
    Run firefox --version or firefox -v to get the installed version number
    Affected if Firefox version is below 107.0 (any version starting with 106.x or earlier)
  3. Determine Firefox ESR version
    Run firefox-esr --version or firefox-esr -v to get the installed version number
    Affected if Firefox ESR version is below 102.6 (any version starting with 102.5 or earlier, or 102.x versions below 102.6)
  4. Determine Thunderbird version
    Run thunderbird --version or thunderbird -v to get the installed version number
    Affected if Thunderbird version is below 102.6 (any version starting with 102.5 or earlier, or versions below 102.6)
  5. Verify WebGL availability (optional context)
    In the browser, navigate to a page that uses WebGL or check about:support for WebGL renderer info
    Affected if WebGL is available or enabled (the vulnerability exists in the WebGL extension code for affected versions regardless, but this confirms the component is present)

You are affected if any installed Mozilla product (Firefox < 107.0, Firefox ESR < 102.6, or Thunderbird < 102.6) has WebGL functionality present in the environment.

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 / 107.0 or later
Fixed in 102.6107.0
Interim mitigation

Update affected products to Firefox 107+, Firefox ESR 102.6+, or Thunderbird 102.6+ to patch the vulnerability.

Recommended fix High confidence

Firefox 107.0, Firefox ESR 102.6, Thunderbird 102.6

  1. Back up all browser profiles and extensions data
  2. Download the latest Firefox 107.0+ (or Firefox ESR 102.6+) from the official Mozilla website at https://www.mozilla.org/
  3. Close all running instances of Firefox or Thunderbird
  4. Run the installer for the new version
  5. After installation, verify the version by navigating to Help > About Firefox (or About Thunderbird)
  6. Ensure the displayed version matches or exceeds 107.0 for Firefox or 102.6 for Firefox ESR/Thunderbird
  7. Re-install any disabled extensions that may have been affected
Caveat Minor version upgrades typically do not introduce breaking changes; however, some legacy extensions or plugins may require updates

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
  • Testing1.0 h
  • Review / QA1.0 h
5.0 hours of engineering $890
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,424.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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