ChromeWeb browser · Google
CVE-2021-4061
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 · uneditedType confusion in V8 in Google Chrome prior to 96.0.4664.93 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 confidenceType confusion vulnerability in Google Chrome's V8 JavaScript engine prior to version 96.0.4664.93 allows remote attackers to potentially exploit heap corruption via a crafted HTML page, potentially leading to arbitrary code execution.
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
< 96.0.4664.93
FedoraOperating system
= 34
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, click the three-dot menu, go to Help > About Google Chrome, or enter chrome://version in the address barAffected if The displayed version is earlier than 96.0.4664.93
-
Check Chrome version on FedoraRun 'rpm -q google-chrome-stable' in terminalAffected if The returned package version is earlier than 96.0.4664.93-1
-
Check Chrome version on Debian/UbuntuRun 'dpkg -l | grep google-chrome' or 'apt-cache policy google-chrome-stable' in terminalAffected if The installed package version is earlier than 96.0.4664.93-1
-
Verify V8 engine componentThe V8 JavaScript engine is embedded within Chrome itself; the vulnerability is present if Chrome version is below the threshold regardless of specific V8 configurationAffected if Chrome is running and its version is earlier than 96.0.4664.93
You are affected if Google Chrome is installed and its version is earlier than 96.0.4664.93, regardless of the operating system.
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 · scoped96.0.4664.93
Upgrade Google Chrome to version 96.0.4664.93 or later to remediate this vulnerability.
Chrome/Chromium 96.0.4664.93 or later
- Check current Chrome/Chromium version by navigating to chrome://version or running `chromium --version`
- Update your package repository: On Fedora run `sudo dnf check-update` or on Debian/Ubuntu run `sudo apt update`
- Upgrade Chrome/Chromium: On Fedora run `sudo dnf update chromium` or on Debian run `sudo apt upgrade chromium`
- Restart the browser completely (close all instances)
- Verify the version is now 96.0.4664.93 or later by checking chrome://version
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation4.0 h
- Implementation8.0 h
- Testing4.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 $5,120.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-4061 — 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-4061 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