ChromeWeb browser · Google
CVE-2021-37978
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 · uneditedHeap buffer overflow in Blink in Google Chrome prior to 94.0.4606.81 allowed a remote attacker 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 confidenceHeap buffer overflow vulnerability in Google Chrome's Blink rendering engine that can be triggered by a specially crafted HTML page, potentially allowing a remote attacker to exploit heap corruption.
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.81
FedoraOperating system
= 33
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 Google Chrome versionOpen chrome://version in the browser address bar or go to Menu > Help > About Google ChromeAffected if The displayed version is earlier than 94.0.4606.81
-
Check Chromium version on LinuxRun 'chromium --version' or 'chromium-browser --version' in terminalAffected if The displayed version is earlier than 94.0.4606.81
-
Check Fedora package versionRun 'rpm -q chromium' if Chromium is installed on Fedora 33Affected if The package version is earlier than the fixed version available in Fedora 33 updates
-
Check Debian package versionRun 'dpkg -l chromium' or 'apt show chromium' on Debian 10 or 11Affected if The installed Chromium package version is earlier than the fixed version for your Debian release
You are affected if Google Chrome or Chromium (on Fedora 33, Debian 10, or Debian 11) is installed with a version number lower than 94.0.4606.81, as the heap buffer overflow in the Blink rendering engine triggers when rendering any HTML content.
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.81
Update Google Chrome to version 94.0.4606.81 or later to patch the vulnerability.
Chrome/Chromium 94.0.4606.81 or later
- For Chrome browser: Open Chrome, go to Settings > Help > About Google Chrome, and click 'Update Google Chrome' to upgrade to version 94.0.4606.81 or later
- For Fedora 33: Run 'sudo dnf update chromium' or 'sudo dnf update google-chrome-stable' to apply the security update
- For Debian 10/11: Run 'sudo apt update && sudo apt upgrade' to install the updated chromium package
- Alternatively, download the latest Chrome stable from google.com/chrome and reinstall
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 / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,848.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-37978 — 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-37978 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