ChromeWeb browser · Google
CVE-2021-21220
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 · uneditedInsufficient validation of untrusted input in V8 in Google Chrome prior to 89.0.4389.128 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 confidenceInsufficient validation of untrusted input in Google Chrome's V8 JavaScript engine prior to version 89.0.4389.128 allows a remote attacker to 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
< 89.0.4389.128
FedoraOperating system
= 32= 33= 34CVSS 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 installedOn Windows, check for Chrome in Program Files or via Registry. On macOS, check /Applications/Google Chrome.app. On Linux, check if 'google-chrome' or 'google-chrome-stable' command exists (e.g., which google-chrome).Affected if Google Chrome is not installed on the system
-
Determine the installed Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' (Linux/macOS) or check the version property in the executable (Windows).Affected if Unable to determine the installed version
-
Compare version against vulnerable rangeCompare the installed version number to 89.0.4389.128. Versions are formatted as major.minor.build.patch (e.g., 89.0.4389.128).Affected if The installed version is less than 89.0.4389.128 (e.g., 88.x.x.x or 89.0.4389.100)
-
Confirm V8 JavaScript engine is in useThis vulnerability affects the V8 engine which is the default JavaScript engine in Chrome. Verify Chrome is using its default settings and not an alternative browser engine.Affected if Chrome is using a non-default JavaScript engine (unlikely for standard Chrome installations)
A user is affected if Google Chrome is installed and the running version is lower than 89.0.4389.128.
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 · scoped89.0.4389.128
Update Google Chrome to version 89.0.4389.128 or later to obtain the patched V8 engine with proper input validation.
Chrome 89.0.4389.128 or later stable release
- 1. Open Chrome and navigate to chrome://settings/help to check current version
- 2. If version is below 89.0.4389.128, download the latest stable Chrome from https://www.google.com/chrome/
- 3. Install the downloaded Chrome version 89.0.4389.128 or later
- 4. Restart Chrome to apply the update
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation1.0 h
- Implementation2.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 $1,664.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21220 — 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-21220 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