ChromeWeb browser · Google
CVE-2021-37974
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 · uneditedUse after free in Safebrowsing in Google Chrome prior to 94.0.4606.71 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 confidenceUse-after-free vulnerability in Google Chrome's Safebrowsing component that allows a remote attacker with a compromised renderer process to potentially exploit heap corruption via a crafted HTML page. The vulnerability exists in versions prior to 94.0.4606.71.
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
< 94.0.4606.71
FedoraOperating system
= 33= 34= 35
Debian LinuxOperating system
= 10.0= 11.0CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check installed Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in terminalAffected if Version is less than 94.0.4606.71
-
Verify Safebrowsing is enabledGo to chrome://settings/security and confirm 'Safe Browsing' protection is turned on (this is the default and required state for the vulnerability to be relevant)Affected if Safebrowsing is enabled and Chrome version is below 94.0.4606.71
-
Check Linux package version on FedoraRun 'rpm -q google-chrome-stable' to query the installed package versionAffected if Package version is less than 94.0.4606.71-1
-
Check Linux package version on DebianRun 'dpkg -l | grep google-chrome-stable' to query the installed package versionAffected if Package version is less than 94.0.4606.71-1
You are affected if you are running Google Chrome (or a chromium-browser package from Fedora or Debian) with a version earlier than 94.0.4606.71 and have Safebrowsing protection enabled (the default setting).
Generated from the published advisory. Verify against your own configuration.
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 · scoped94.0.4606.71
Update Google Chrome to version 94.0.4606.71 or later to remediate this vulnerability. Organizations should deploy browser updates through their patch management infrastructure and verify completion across affected endpoints.
Chrome 94.0.4606.71 or later (or patched chromium package for Linux distributions)
- Update Google Chrome to version 94.0.4606.71 or later by navigating to Chrome Menu > Help > About Google Chrome and clicking 'Update Chrome'
- Alternatively, download the latest stable Chrome from the official Google website
- For Linux distributions (Fedora/Debian), run 'sudo dnf update' or 'sudo apt update && sudo apt upgrade' to receive the patched Chromium package
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
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 locallyCheck whether your project pulls in CVE-2021-37974 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2021-37974 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
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.
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.
- 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