ChromeWeb browser · Google
CVE-2021-30541
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 V8 in Google Chrome prior to 91.0.4472.164 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 V8 JavaScript engine in Google Chrome prior to version 91.0.4472.164 allows remote attackers to 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
< 91.0.4472.164CVSS 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 Chrome versionOpen Chrome and navigate to chrome://version, or click the three-dot menu > Help > About Google Chrome. Note the version number displayed.Affected if The displayed version is less than 91.0.4472.164 (for example, 91.0.4472.101, 90.x, or earlier).
-
Check Chrome channel if version is unclearIn chrome://version, look for the 'Profile Path' line or check if the browser was installed via an enterprise policy. Enterprise deployments may use different version numbering.Affected if Running a version obtained through enterprise deployment that reports a build number lower than 91.0.4472.164.
-
Verify V8 JavaScript engine is presentThe V8 engine is built into Chrome and cannot be disabled. No separate check is needed; any standard Chrome installation includes V8.Affected if Chrome is installed and running, meaning V8 is present and vulnerable if the version condition above is met.
A user is affected if Google Chrome is installed with a version number less than 91.0.4472.164, as this version range contains the vulnerable V8 JavaScript engine.
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.164
Update Google Chrome to version 91.0.4472.164 or later; in enterprise environments, deploy the update via patch management systems to ensure all affected installations are remediated.
91.0.4472.164
- Open Google Chrome and navigate to chrome://settings/help to check the current version
- If the installed version is earlier than 91.0.4472.164, initiate the update process
- Chrome will automatically download and install the latest update; wait for the download to complete
- If automatic updates are not available, download the latest stable Chrome version directly from the official website at https://www.google.com/chrome/
- Install the downloaded Chrome installer
- Restart Google Chrome after the update is complete to ensure all components are properly updated
- Verify the version now shows 91.0.4472.164 or later by returning to chrome://settings/help
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.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,744.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-30541 — 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-30541 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