ChromeWeb browser · Google
CVE-2021-21224
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 90.0.4430.85 allowed a remote attacker to execute arbitrary code inside a sandbox 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 Chrome's V8 JavaScript engine allows a remote attacker to execute arbitrary code via a crafted HTML page. The vulnerability exists prior to Chrome version 90.0.4430.85 and exploits the type system to cause memory corruption leading to code execution within the sandbox context.
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
< 90.0.4430.85
Debian LinuxOperating system
= 10.0
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.
-
Verify Google Chrome is installedCheck for Chrome executable or run 'google-chrome --version' in terminal. On Windows check C:\Program Files\Google\Chrome\Application\chrome.exe. On macOS check /Applications/Google Chrome.app.Affected if Google Chrome browser is present on the system
-
Determine installed Chrome versionRun 'google-chrome --version' on Linux, or on Windows/macOS navigate to chrome://settings/help to view the version number.Affected if Version returned is below 90.0.4430.85 (for example, 89.0.4389.114 or earlier)
-
Check for Chromium-based browsers (alternative detection)Some browsers like Microsoft Edge, Brave, or Opera are built on Chromium. Run 'edge --version' or check respective version locations.Affected if A Chromium-based browser is installed with a version corresponding to Chrome < 90.0.4430.85 (watch for version 89.x or earlier)
The user is affected if Google Chrome or any Chromium-based browser with version numbers matching Chrome versions prior to 90.0.4430.85 is installed and actively used.
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 · scoped90.0.4430.85
Update Google Chrome to version 90.0.4430.85 or later to patch the V8 type confusion vulnerability. Deploy via standard patch management processes and verify the update was applied.
Chrome version 90.0.4430.85 or later
- Open Chrome and navigate to Settings > Help > About Google Chrome to check current version
- If version is below 90.0.4430.85, Chrome will automatically check for updates - click 'Update Google Chrome' if available
- Restart Chrome after the update completes
- If automatic update is not available, download the latest stable Chrome from the official Google Chrome website (google.com/chrome) and reinstall
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
- Implementation1.0 h
- Testing1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21224 — 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-21224 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