dbcve.org
Actively exploited in the wild. This CVE is on the CISA Known Exploited Vulnerabilities list — treat remediation as urgent. Federal remediation due by 29 Dec 2021.
ChromeWeb browser · Google

CVE-2021-4102

HIGH · 8.8 CVSS v3.1 Published 2022-02-11
Fix available
A fix is available. Upgrade to 96.0.4664.110 or later.
See remediation →
100/100
Remediation priority · Urgent
In the wild 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 V8 in Google Chrome prior to 96.0.4664.110 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 Chrome's V8 JavaScript engine that allows a remote attacker to potentially exploit heap corruption by tricking users into visiting a crafted HTML page.

MitigationUpdate Google Chrome to version 96.0.4664.110 or later to patch the vulnerability.

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:< 96.0.4664.110

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. Identify if Google Chrome is installed
    Locate the Google Chrome browser executable on the system (common paths include C:\Program Files\Google\Chrome\Application\chrome.exe on Windows, /Applications/Google Chrome.app on macOS, or /usr/bin/google-chrome on Linux)
    Affected if Google Chrome is found on the system and the installed version is below 96.0.4664.110
  2. Determine the installed Chrome version
    On Windows, right-click the Chrome shortcut and select Properties, then view the Details tab for the Version field. On macOS, open Chrome, click Chrome menu, select About Google Chrome. On Linux, run 'google-chrome --version' or check the package manager.
    Affected if The displayed version number is less than 96.0.4664.110 (for example, 96.0.4664.93 or earlier)
  3. Verify the V8 engine component version
    Open Google Chrome, navigate to chrome://version, and locate the V8 version information displayed on that page
    Affected if The V8 version corresponds to a Chrome version below 96.0.4664.110

The environment is affected if Google Chrome is installed and its version is lower than 96.0.4664.110, as this specific range contains the use-after-free vulnerability in the V8 JavaScript engine.

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 96.0.4664.110 or later
Fixed in 96.0.4664.110
Interim mitigation

Update Google Chrome to version 96.0.4664.110 or later to patch the vulnerability.

Recommended fix High confidence

Chrome 96.0.4664.110 or later

  1. 1. Open Chrome and navigate to Help > About Google Chrome to check the current version.
  2. 2. If the version is below 96.0.4664.110, download Chrome version 96.0.4664.110 or later from the official Chrome download page (google.com/chrome).
  3. 3. Install the updated Chrome version.
  4. 4. Restart the browser to complete the update.

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
  • Implementation3.0 h
  • Testing2.0 h
  • Review / QA1.0 h
8.0 hours of engineering $1,420
Get it fixed fast

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,272.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2021-4102 — 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-4102 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