ChromeWeb browser · Google
CVE-2021-21115
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 · uneditedUser after free in safe browsing in Google Chrome prior to 87.0.4280.141 allowed a remote attacker who had compromised the renderer process to potentially perform a sandbox escape 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 Safe Browsing feature prior to version 87.0.4280.141 allows a remote attacker who has already compromised the renderer process to potentially escape the sandbox 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
< 87.0.4280.141
FedoraOperating system
= 32= 33
Debian LinuxOperating system
= 10.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
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:C/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 in the Chrome browser, or run 'google-chrome --version' or 'chrome --version' from command lineAffected if The displayed version is less than 87.0.4280.141 (e.g., 87.0.4280.x where x < 141, or any version 86.x, 85.x, etc.)
-
Check Chrome package version on FedoraRun 'rpm -qa | grep chrome' to list installed Chrome packages, then check the version with 'rpm -q google-chrome-stable'Affected if The installed google-chrome-stable package version is lower than 87.0.4280.141-1
-
Check Chrome package version on DebianRun 'dpkg -l | grep google-chrome' or 'apt list --installed | grep google-chrome' to list installed packages and their versionsAffected if The installed google-chrome-stable package version is lower than 87.0.4280.141-1
A user is affected if they are running any version of Google Chrome older than 87.0.4280.141, or have the vulnerable package installed on Fedora 32/33 or Debian 10.0.
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 · scoped87.0.4280.141
Upgrade Google Chrome to version 87.0.4280.141 or later to remediate this vulnerability.
Chrome 87.0.4280.141 or later
- For Chrome browser users: Navigate to chrome://settings/help and click 'Update Google Chrome' to install version 87.0.4280.141 or later
- For Fedora systems (versions 32 and 33): Run 'sudo dnf update google-chrome-stable' to apply the security patch
- For Debian 10 systems: Run 'sudo apt update && sudo apt upgrade google-chrome-stable' to install the patched version
- After updating, restart the Chrome browser to ensure the vulnerability is fully mitigated
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation1.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,200.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21115 — 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-21115 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