ChromeWeb browser · Google
CVE-2021-4065
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 96.0.4664.93 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 exists in the autofill component of Google Chrome versions prior to 96.0.4664.93. A remote attacker can exploit this by tricking a user into visiting a crafted HTML page, potentially leading to heap corruption and 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
< 96.0.4664.93
FedoraOperating system
= 34
Debian LinuxOperating system
= 10.0= 11.0CVSS 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 installed Google Chrome versionNavigate to chrome://settings/help or click Help > About Google Chrome to view the installed version numberAffected if The displayed version is less than 96.0.4664.93
-
Check Chrome package version on Fedora 34Run command: rpm -q google-chrome-stable and compare the version number to 96.0.4664.93Affected if The installed package version is lower than 96.0.4664.93
-
Check Chrome package version on Debian 10.0 or 11.0Run command: dpkg -l | grep google-chrome-stable or apt-cache policy google-chrome-stableAffected if The installed package version is lower than 96.0.4664.93-1
-
Verify autofill component is presentIn Chrome, go to Settings > Autofill and confirm the autofill feature is available (this component contains the vulnerable code)Affected if Autofill is accessible in the browser settings
The environment is affected if Google Chrome (or the Fedora/Debian chrome package) is installed with a version number below 96.0.4664.93.
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 · scoped96.0.4664.93
Update Google Chrome to version 96.0.4664.93 or later. Organizations should deploy the update through their patch management systems and verify successful installation across endpoints.
Chrome 96.0.4664.93 or later (stable channel)
- Upgrade Google Chrome to version 96.0.4664.93 or later
- On Linux systems, this can typically be done via the system's package manager (e.g., `dnf update chrome` on Fedora, `apt update && apt upgrade` on Debian)
- Alternatively, download the latest stable Chrome from the official Google Chrome website
- After upgrading, restart the browser to ensure the update is fully applied
- Verify the installed version by navigating to chrome://settings/help to confirm version 96.0.4664.93 or newer is installed
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-4065 — 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-4065 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