dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 17 Nov 2021.
ChromeWeb browser · Google

CVE-2021-37976

MEDIUM · 6.5 CVSS v3.1 Published 2021-10-08
Fix available
A fix is available. Upgrade to 94.0.4606.71 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild Public exploit 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
Inappropriate implementation in Memory in Google Chrome prior to 94.0.4606.71 allowed a remote attacker to obtain potentially sensitive information from process memory 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

Memory management flaw in Google Chrome before 94.0.4606.71 allows a remote attacker to read sensitive information from process memory through a malicious HTML page. This is an information disclosure vulnerability stemming from improper memory handling, not code execution.

MitigationUpdate Google Chrome to version 94.0.4606.71 or later to patch the memory implementation flaw. Organizations should ensure all Chrome installations are updated via their patch management processes.

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.71
FedoraOperating system
Affected:= 33= 34= 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
None
Availability
None

CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify your Chrome installation location and method
    Determine if Chrome was installed via official Google packages, system package manager (dnf/apt), or another source. On Linux, run 'which google-chrome' or check your package manager.
    Affected if Chrome is installed via any method - the vulnerability exists in the browser code itself regardless of install source
  2. Determine installed Chrome version
    Open Chrome and navigate to chrome://settings/help, or from command line run 'google-chrome --version' on Linux, 'C:\Program Files\Google\Chrome\Application\chrome.exe --version' on Windows, or 'open -a "Google Chrome" --args --version' on macOS.
    Affected if The displayed version number is lower than 94.0.4606.71
  3. Verify package manager version on Fedora
    If using Fedora, run 'dnf list installed | grep google-chrome' or 'rpm -qa | grep google-chrome' to see the installed package version.
    Affected if The reported package version is less than 94.0.4606.71
  4. Verify package manager version on Debian
    If using Debian, run 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' to see the installed package version.
    Affected if The reported package version is less than 94.0.4606.71
  5. Confirm browser is actively used
    Determine whether Chrome is the primary or regular browser on this system, since the vulnerability requires a user to visit a malicious HTML page.
    Affected if Users on this system actively browse the web using Google Chrome

If the installed Google Chrome version is below 94.0.4606.71 and users browse the web with this browser, the environment is affected by this information disclosure vulnerability.

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.71 or later
Fixed in 94.0.4606.71
Interim mitigation

Update Google Chrome to version 94.0.4606.71 or later to patch the memory implementation flaw. Organizations should ensure all Chrome installations are updated via their patch management processes.

Recommended fix High confidence

Chrome 94.0.4606.71 or later; Fedora and Debian should update to their patched chromium package versions

  1. Update Google Chrome to version 94.0.4606.71 or later by navigating to Chrome menu > Help > About Google Chrome and clicking 'Update'
  2. For Fedora systems: Run 'sudo dnf update chromium' or 'sudo dnf update google-chrome-*' to apply the security update
  3. For Debian systems: Run 'sudo apt update && sudo apt upgrade' to apply the security update for chromium or google-chrome-stable packages
  4. Restart the browser after updating to ensure the fix is applied

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

Fix this in Chrome Exploited in the wild — priority engagement
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get it fixed fast

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-37976 — 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-37976 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