ChromeWeb browser · Google
CVE-2021-21193
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 · uneditedUse after free in Blink in Google Chrome prior to 89.0.4389.90 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 confidenceUse after free vulnerability in Chrome's Blink rendering engine that allows a remote attacker to potentially exploit heap corruption via a crafted HTML page.
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.90
FedoraOperating system
= 32
Debian LinuxOperating system
= 10.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 Chrome browser versionNavigate to chrome://version in the Chrome browser or run 'google-chrome --version' (Linux) / 'chrome --version' (Windows) / '/Applications/Google\ Chrome.app/Contents/MacOS/Google\ Chrome --version' (Mac)Affected if The displayed version is lower than 89.0.4389.90
-
Verify Chrome package version on FedoraRun 'dnf list installed google-chrome' or 'rpm -q google-chrome'Affected if The installed package version is less than 89.0.4389.90-1
-
Verify Chrome package version on DebianRun 'dpkg -l google-chrome-stable' or 'apt-cache policy google-chrome-stable'Affected if The installed package version is less than 89.0.4389.90-1
-
Confirm Blink rendering engine is in useNavigate to chrome://components and verify Blink is present, or check that no third-party engine replacement is configuredAffected if The default Blink rendering engine is active (this is the default for standard Chrome installations)
You are affected if Google Chrome version is below 89.0.4389.90 and the default Blink rendering engine is in use.
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.90
Update Google Chrome to version 89.0.4389.90 or later to patch the vulnerability.
Chrome/Chromium 89.0.4389.90 or later
- For Chrome/Chromium browsers: Navigate to Chrome menu > Help > About Google Chrome and verify version is 89.0.4389.90 or later, or download the latest version from official Google Chrome channels
- For Fedora 32 systems: Run 'sudo dnf update' or 'sudo dnf upgrade' to apply security updates including the Chrome browser update
- For Debian 10 (Buster) systems: Run 'sudo apt update && sudo apt upgrade' to install the latest Chromium browser security updates
- Verify the installed Chrome/Chromium version matches or exceeds 89.0.4389.90 after updating
- Clear browser cache and restart the browser to ensure the patched version is fully loaded
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-21193 — 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-21193 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