ChromeWeb browser · Google
CVE-2021-21121
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 Omnibox in Google Chrome on Linux prior to 88.0.4324.96 allowed a remote attacker 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 exists in the Omnibox (URL bar) component of Google Chrome on Linux versions prior to 88.0.4324.96. The vulnerability allows a remote attacker to exploit freed memory through a specially crafted HTML page, potentially achieving sandbox escape and executing arbitrary code with elevated privileges.
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
< 88.0.4324.96< 88.0.705.50CVSS 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 Google Chrome version on LinuxOpen terminal and run: google-chrome --version or chrome --versionAffected if Version is lower than 88.0.4324.96
-
Check Microsoft Edge Chromium versionOpen terminal and run: microsoft-edge --version or edge --versionAffected if Version is lower than 88.0.705.50
-
Verify browser is running on LinuxRun: uname -a or cat /etc/os-releaseAffected if Running Google Chrome on Linux and version is below 88.0.4324.96 (Edge affects multiple OS versions below 88.0.705.50)
-
Confirm Omnibox component is in useThe Omnibox (URL bar) is active by default in Chrome and Edge browsers - no manual check neededAffected if Browser is actively used for web navigation (Omnibox is the default URL bar in Chrome/Edge)
-
Check for elevated privilegesReview browser process privileges: ps aux | grep -i chrome or check if running with sandbox disabledAffected if Browser is running with elevated privileges or sandbox disabled, increasing exploit impact
You are affected if running Google Chrome on Linux below version 88.0.4324.96 or Microsoft Edge Chromium below version 88.0.705.50, with the Omnibox (URL bar) in active use.
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 · scoped88.0.705.5088.0.4324.96
Organizations should immediately update Google Chrome for Linux to version 88.0.4324.96 or later to patch this critical vulnerability. Until patched, restrict access to untrusted websites and disable unnecessary extensions to reduce attack surface.
Chrome: 88.0.4324.96+ | Edge Chromium: 88.0.705.50+
- Update Google Chrome to version 88.0.4324.96 or later
- Update Microsoft Edge Chromium to version 88.0.705.50 or later
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-21121 — 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-21121 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