ChromeWeb browser · Google
CVE-2021-38007
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.45 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 allows a remote attacker to potentially exploit heap corruption via a crafted HTML page. The vulnerability stems from improper type handling in V8 that can lead to memory corruption and potentially remote 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.45
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 if Google Chrome is installedLook for the Chrome binary: on Linux check /usr/bin/google-chrome or /opt/google/chrome/chrome; on Windows check C:\Program Files\Google\Chrome\Application\chrome.exe or C:\Program Files (x86)\Google\Chrome\Application\chrome.exeAffected if Chrome browser is present on the system
-
Determine installed Chrome versionRun 'google-chrome --version' on Linux or 'chrome --version' on Windows command line, or right-click chrome.exe and select Properties > Details to view the File VersionAffected if The command returns a version number lower than 96.0.4664.45
-
Confirm V8 JavaScript engine is in useThis is implicit when Chrome is running JavaScript - visit chrome://version to confirm the browser is operational and see the V8 engine version listedAffected if Chrome with V8 engine is running and the version from step 2 is below 96.0.4664.45
A user is affected if Google Chrome is installed and its version is lower than 96.0.4664.45, as this version range contains the vulnerable V8 JavaScript engine with the type confusion flaw.
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.45
Update Google Chrome to version 96.0.4664.45 or later to patch the V8 type confusion vulnerability.
96.0.4664.45 or later
- Open Google Chrome browser
- Navigate to chrome://settings/help or go to Settings > About Chrome
- Chrome automatically checks for updates; if an update to version 96.0.4664.45 or later is available, click 'Update Google Chrome'
- Restart the browser to apply the update
- Alternatively, on Linux systems, update via package manager: sudo dnf update google-chrome-stable (Fedora) or sudo apt update && sudo apt upgrade google-chrome-stable (Debian)
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.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,880.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-38007 — 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-38007 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