dbcve.org
ChromeWeb browser · Google

CVE-2021-37956

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 Offline use in Google Chrome on Android prior to 94.0.4606.54 allowed a remote attacker who had compromised the renderer process 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 Offline component on Android before version 94.0.4606.54 allows a remote attacker with a compromised renderer process to potentially exploit heap corruption via a crafted HTML page.

MitigationUpdate Google Chrome for Android to version 94.0.4606.54 or later. For enterprise environments, use mobile device management to ensure Chrome updates are pushed to managed devices.

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 Chrome for Android is installed
    Open device Settings > Apps > Chrome, or check the app version directly from the Google Play Store if installed
    Affected if Chrome for Android is installed on the device
  2. Identify the installed Chrome for Android version
    Navigate to Settings > Apps > Chrome > App info, or enter chrome://version in the Chrome address bar to view the version number
    Affected if The displayed version is below 94.0.4606.54 (for example, 94.0.4606.53 or earlier)
  3. Confirm the Offline component is accessible
    The Offline component is part of Chrome for Android's offline pages and download functionality accessible via chrome://offline (or by attempting to use offline mode). This component is built into Chrome and cannot be independently disabled.
    Affected if Chrome for Android is in use and the version is below 94.0.4606.54, meaning the vulnerable Offline component code is present

You are affected if Google Chrome for Android is installed and its version is earlier than 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 for Android to version 94.0.4606.54 or later. For enterprise environments, use mobile device management to ensure Chrome updates are pushed to managed devices.

Recommended fix High confidence

Chrome 94.0.4606.54 or later (or Chromium packages from Fedora 33/35 and Debian 10/11 that contain this security fix)

  1. Check current Chrome version by navigating to chrome://version or chrome://settings/help
  2. For Chrome on Android: Update the app through Google Play Store to version 94.0.4606.54 or later
  3. For Chrome on Desktop: Click Help > About Google Chrome and ensure version is 94.0.4606.54 or later, then restart the browser
  4. For Fedora systems: Run 'sudo dnf update chromium' or 'sudo dnf update google-chrome-*' to install the patched version
  5. For Debian systems: Run 'sudo apt update && sudo apt upgrade' to install the patched Chrome/Chromium package
  6. Restart the browser after updating to apply the fix
Caveat Minimal risk - this is a security patch within the same major version; users should update as soon as possible

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

Fix this in Chrome Scoped from the published advisory
  • Consultation1.0 h
  • Implementation1.0 h
  • Testing1.0 h
  • Review / QA1.0 h
4.0 hours of engineering $750
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,200.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

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