dbcve.org
ChromeWeb browser · Google

CVE-2021-37959

HIGH · 8.8 CVSS v3.1 Published 2021-10-08
Fix available
A fix is available. Upgrade to 94.0.4606.54 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
Use after free in Task Manager in Google Chrome prior to 94.0.4606.54 allowed an attacker who convinced a user to enage in a series of user gestures to potentially exploit heap corruption via a crafted HTML page.

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

Use-after-free vulnerability in Google Chrome's Task Manager component affecting versions prior to 94.0.4606.54. An attacker could exploit this by tricking a user into performing a series of user gestures on a crafted HTML page, potentially leading to heap corruption.

MitigationUpdate Google Chrome to version 94.0.4606.54 or later. Organizations should deploy the latest browser version across all endpoints.

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
ChromeWeb browser
Affected:< 94.0.4606.54
FedoraOperating system
Affected:= 33= 35
Debian LinuxOperating system
Affected:= 10.0= 11.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
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. Check if Google Chrome is installed
    On Windows: Check for chrome.exe in Program Files or AppData. On Linux: Run 'which google-chrome' or check /usr/bin/google-chrome. On macOS: Check /Applications/Google Chrome.app
    Affected if Google Chrome is installed on the system
  2. Determine installed Chrome version
    Open Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' on Linux/macOS. On Windows, check file properties of chrome.exe or use registry key under HKLM\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\Google Chrome
    Affected if Version is lower than 94.0.4606.54 (e.g., 93.x, 92.x, etc.)
  3. Verify Task Manager component is accessible
    Open Chrome, press Shift+Escape or go to chrome://taskmanager to confirm Task Manager functionality is available
    Affected if Task Manager opens successfully (the vulnerable component is present and accessible)
  4. Check OS package versions on Fedora/Debian
    On Fedora: Run 'dnf list installed | grep chrome' or 'rpm -q google-chrome-stable'. On Debian: Run 'dpkg -l | grep google-chrome'
    Affected if Package version is below 94.0.4606.54 on Fedora 33/35 or Debian 10.0/11.0

A user is affected if Google Chrome version 94.0.4606.54 or higher is not installed and the browser is in use, since the vulnerability exists in the Task Manager component of versions prior to 94.0.4606.54.

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 94.0.4606.54 or later
Fixed in 94.0.4606.54
Interim mitigation

Update Google Chrome to version 94.0.4606.54 or later. Organizations should deploy the latest browser version across all endpoints.

Recommended fix High confidence

Chrome 94.0.4606.54 or later

  1. Update Google Chrome to version 94.0.4606.54 or later by navigating to Chrome menu > Help > About Google Chrome and allowing the automatic update to complete
  2. Restart Chrome after the update is installed
  3. Verify the installed version by going to chrome://settings/help - it should show version 94.0.4606.54 or higher
  4. For Fedora systems: run 'sudo dnf update google-chrome-stable' to update the package
  5. For Debian systems: run 'sudo apt update && sudo apt upgrade' to apply the security update

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

Fix this in Chrome 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-2021-37959 — 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-2021-37959 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