ChromeWeb browser · Google
CVE-2021-21206
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.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 confidenceUse after free vulnerability in Google Chrome's Blink rendering engine (versions prior to 89.0.4389.128) allows a remote attacker to potentially exploit heap corruption via a crafted HTML page, leading to possible 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.
-
Determine installed Google Chrome versionOpen Chrome and navigate to chrome://settings/help, or run 'google-chrome --version' from command line on Linux, or 'Google Chrome > About Google Chrome' on MacAffected if Version displayed is less than 89.0.4389.128 (e.g., 89.0.4389.114 or earlier)
-
Confirm Chromium-based browser version on FedoraRun 'rpm -q chromium' or 'dnf list installed chromium' to check if the chromium package is installedAffected if Package version is installed from Fedora 32, 33, or 34 repositories and is older than the patched version shipped for those releases
-
Verify browser is using the vulnerable Blink engineNavigate to chrome://version in the browser and confirm the Blink version is displayed in the User-Agent string or component listAffected if The browser runs Blink and the underlying version matches the vulnerable Chrome version range
A user is affected if their Google Chrome or Chromium browser version is below 89.0.4389.128, or if they are running a Chromium package from Fedora 32, 33, or 34 that has not been patched.
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 patch the use-after-free vulnerability in the Blink rendering engine.
Chrome 89.0.4389.128 or later
- 1. Open Google Chrome and navigate to Settings > Help > About Google Chrome
- 2. Chrome will automatically check for updates and display the current version
- 3. If Chrome is older than 89.0.4389.128, click 'Update Google Chrome' (or wait for automatic update to complete)
- 4. Restart Chrome to apply the update
- 5. Alternatively, manually download the latest Chrome version from https://www.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
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21206 — 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-21206 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