dbcve.org
ChromeWeb browser · Google

CVE-2021-21203

HIGH · 8.8 CVSS v3.1 Published 2021-04-26
Fix available
A fix is available. Upgrade to 90.0.4430.72 or later.
See remediation →
95/100
Remediation priority · Urgent
Remotely reachable No privileges

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 · unedited
Use after free in Blink in Google Chrome prior to 90.0.4430.72 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 confidence

Use after free vulnerability in the Blink rendering engine of Google Chrome prior to version 90.0.4430.72 allows remote attackers to potentially exploit heap corruption via a specially crafted HTML page.

MitigationUpdate Google Chrome to version 90.0.4430.72 or later to patch the vulnerability. Organizations should deploy the update across all affected endpoints.

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
Affected:< 90.0.4430.72
Debian LinuxOperating system
Affected:= 10.0
FedoraOperating system
Affected:= 32= 33= 34

CVSS 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 checks

Work through these to decide whether this CVE applies to you.

  1. Check Google Chrome version on Windows or macOS
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or run 'google-chrome --version' in command prompt/Terminal
    Affected if Version displayed is less than 90.0.4430.72
  2. Check Chromium package version on Debian Linux
    Run 'dpkg -l | grep chromium' or 'apt-cache policy chromium' in terminal
    Affected if Installed chromium version is lower than the version shipped in 90.0.4430.72 for Debian 10
  3. Check Chromium package version on Fedora Linux
    Run 'rpm -qa | grep chromium' or 'dnf list installed chromium' in terminal
    Affected if Installed chromium version is lower than the version shipped in 90.0.4430.72 for Fedora 32, 33, or 34
  4. Check Google Chrome package version on Linux
    Run 'google-chrome --version' or 'rpm -qa | grep google-chrome' in terminal
    Affected if Version is less than 90.0.4430.72

You are affected if Google Chrome or the Chromium package installed on your system is any version prior to 90.0.4430.72.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 90.0.4430.72 or later
Fixed in 90.0.4430.72
Interim mitigation

Update Google Chrome to version 90.0.4430.72 or later to patch the vulnerability. Organizations should deploy the update across all affected endpoints.

Recommended fix High confidence

Chrome 90.0.4430.72 or later

  1. Update Google Chrome to version 90.0.4430.72 or later by visiting chrome://settings/help and clicking 'Update Google Chrome', or use your system's package manager to update the chrome or chromium package

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation3.0 h
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA2.0 h
10.0 hours of engineering $1,800
Get the upgrade done

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 locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-21203 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2021-21203 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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