dbcve.org
ChromeWeb browser · Google

CVE-2021-37997

HIGH · 8.8 CVSS v3.1 Published 2021-11-23
Fix available
A fix is available. Upgrade to 95.0.4638.69 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 Sign-In in Google Chrome prior to 95.0.4638.69 allowed a remote attacker who convinced a user to sign into Chrome 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 Sign-In functionality prior to version 95.0.4638.69 allows a remote attacker who convinces a user to sign into Chrome while visiting a crafted HTML page to potentially exploit heap corruption, which could lead to arbitrary code execution.

MitigationUpgrade Google Chrome to version 95.0.4638.69 or later. Organizations should deploy browser updates through their patch management systems to ensure all instances are remediated.

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:< 95.0.4638.69
FedoraOperating system
Affected:= 34
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 installed Chrome version on Windows or Mac
    Open Chrome and navigate to chrome://version, or click Help > About Google Chrome. Note the version number displayed.
    Affected if Version number is less than 95.0.4638.69
  2. Check Chrome version on Linux via command line
    Run 'google-chrome --version' or 'chromium --version' in a terminal.
    Affected if Version number is less than 95.0.4638.69
  3. Check installed package version on Fedora 34
    Run 'rpm -q google-chrome' or 'dnf list installed | grep chrome' in a terminal.
    Affected if Package version is less than 95.0.4638.69
  4. Check installed package version on Debian 10 or 11
    Run 'dpkg -l | grep chromium' or 'apt show chromium' in a terminal.
    Affected if Package version is less than 95.0.4638.69
  5. Verify if Chrome profile is signed in
    Open Chrome settings and check if a Google account is signed in under the 'You and Google' section, or inspect chrome://settings for sync status.
    Affected if User has a Google account signed into Chrome (this condition must be met for the vulnerability to be exploitable)

You are affected if you are running any Google Chrome version earlier than 95.0.4638.69 with a Google account signed into the browser.

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

Upgrade Google Chrome to version 95.0.4638.69 or later. Organizations should deploy browser updates through their patch management systems to ensure all instances are remediated.

Recommended fix High confidence

Chrome 95.0.4638.69 or later (including subsequent stable releases)

  1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
  2. Click 'Update Google Chrome' if an update is available, or verify the version is 95.0.4638.69 or later
  3. For Fedora systems: Run 'sudo dnf update chromium' to install the patched version
  4. For Debian systems: Run 'sudo apt update && sudo apt upgrade chromium' to install the patched version
  5. Restart the browser after updating to apply the fix
Caveat Chrome updates typically have minimal breaking changes; some legacy extensions or features may require reinstallation or reconfiguration

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

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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