ChromeWeb browser · Google
CVE-2021-30554
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 WebGL in Google Chrome prior to 91.0.4472.114 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 WebGL implementation prior to version 91.0.4472.114 allows remote attackers to exploit heap corruption via specially crafted HTML pages. The vulnerability occurs when memory is accessed after it has been freed, leading to potential 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
< 91.0.4472.114
FedoraOperating system
= 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 Google Chrome versionNavigate to chrome://version in the Chrome browser or click Help > About Google Chrome to view the installed version numberAffected if The displayed version is earlier than 91.0.4472.114 (e.g., 91.0.4472.101, 90.x, etc.)
-
Check if WebGL is enabledNavigate to chrome://flags in the address bar and search for 'WebGL' or go to chrome://gpu to view WebGL status under Graphics Feature StatusAffected if WebGL is listed as Enabled or Hardware Accelerated (the vulnerability only affects environments where WebGL is active)
-
Verify Fedora version (if using Fedora)Run 'cat /etc/fedora-release' or 'rpm -q fedora-release' in the terminalAffected if Running Fedora 33 or Fedora 34 with Chrome installed from the Fedora repositories
You are affected if Chrome version is below 91.0.4472.114 AND WebGL is enabled in the browser settings.
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 · scoped91.0.4472.114
Update Google Chrome to version 91.0.4472.114 or later. For enterprise environments, deploy the browser update via standard software distribution mechanisms (e.g., Group Policy, SCCM, Intune).
Chrome 91.0.4472.114 or later
- Open Google Chrome
- Navigate to Menu (three dots) > Help > About Google Chrome
- Chrome will automatically check for and download available updates
- If version is below 91.0.4472.114, wait for the update to download and install
- Restart Chrome to complete the update process
- Verify the installed version by returning to Help > About Google Chrome and confirming it shows 91.0.4472.114 or higher
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Exploited in the wild — priority engagement
- Consultation2.0 h
- Implementation4.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30554 — 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-30554 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