ChromeWeb browser · Google
CVE-2021-30546
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 Autofill in Google Chrome prior to 91.0.4472.101 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 confidenceA use-after-free vulnerability in Google Chrome's Autofill feature prior to version 91.0.4472.101 allows a remote attacker to exploit heap corruption through a crafted HTML page, potentially leading to arbitrary 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.101
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.
-
Verify Google Chrome is installedCheck for Chrome executable: On Windows, look for chrome.exe in Program Files or Program Files (x86). On Linux, run 'which google-chrome' or check /usr/bin/google-chrome. On macOS, check /Applications/Google Chrome.appAffected if Chrome is not found on the system, the user is not affected by this specific Chrome vulnerability
-
Determine installed Chrome versionOpen Chrome, navigate to chrome://settings/help, or run 'google-chrome --version' from command line. The version number displays on the About pageAffected if Version is less than 91.0.4472.101 (for example, 91.0.4472.99 or earlier)
-
Confirm Autofill feature is enabledIn Chrome, go to Settings > Autofill and Passwords > Autofill settings, or navigate to chrome://settings/autofillAffected if Autofill is enabled and the browser fills in form data automatically
-
Check if running on affected Fedora versionRun 'cat /etc/fedora-release' to identify the Fedora versionAffected if Running Fedora 33 or Fedora 34 with an older Chrome package installed
User is affected if Chrome version is below 91.0.4472.101 AND the Autofill feature 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.101
Update Google Chrome to version 91.0.4472.101 or later to patch the use-after-free vulnerability in Autofill.
Chrome 91.0.4472.101 or later (or google-chrome-stable on Fedora)
- Update Google Chrome to version 91.0.4472.101 or later
- On Fedora systems, run 'sudo dnf update google-chrome-stable' to apply the security update
- Restart the browser after updating to ensure the fix is applied
- Verify the version by navigating to chrome://settings/help to confirm the installed version
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-30546 — 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-30546 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