ChromeWeb browser · Google
CVE-2021-21132
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 · uneditedInappropriate implementation in DevTools in Google Chrome prior to 88.0.4324.96 allowed a remote attacker to potentially perform a sandbox escape via a crafted Chrome Extension.
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 vulnerability in Google Chrome's DevTools component (versions prior to 88.0.4324.96) allowed a remote attacker to potentially escape the sandbox security boundary by leveraging a specially crafted Chrome Extension. This inappropriate implementation in DevTools could be exploited to perform actions outside the normal sandbox restrictions.
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 versionOpen Chrome, click the three-dot menu, select Help, then About Google Chrome. The version number is displayed on that page.Affected if The displayed version number is less than 88.0.4324.96
-
Check Microsoft Edge Chromium versionOpen Edge, click the three-dot menu, select Help and feedback, then About Microsoft Edge. The version number is displayed on that page.Affected if The displayed version number is less than 88.0.705.50
-
Verify DevTools availabilityOpen any web page in the browser, then press F12 or right-click and select Inspect to open Developer Tools.Affected if DevTools opens successfully (the vulnerability applies whenever DevTools can be accessed, regardless of whether a malicious extension is installed)
You are affected if you are running Google Chrome below version 88.0.4324.96 or Microsoft Edge Chromium below version 88.0.705.50, and your organization permits the use of browser extensions.
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
Update Google Chrome to version 88.0.4324.96 or later to patch the vulnerability. Organizations should deploy Chrome updates across all endpoints and verify successful remediation.
Chrome 88.0.4324.96 or later / Edge Chromium 88.0.705.50 or later
- 1. Open Chrome or Edge Chromium browser
- 2. Navigate to Help > About Google Chrome (or About Microsoft Edge)
- 3. The browser will check for updates and automatically download version 88.0.4324.96 or later for Chrome, or 88.0.705.50 or later for Edge Chromium
- 4. Click 'Restart' to apply the update
- 5. Alternatively, download the latest stable version from the official Chrome or Edge download page
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Chrome
Scoped from the published advisory
- Consultation2.0 h
- Implementation4.0 h
- Testing2.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 $2,560.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21132 — 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-21132 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