ChromeWeb browser · Google
CVE-2021-21146
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 Navigation in Google Chrome prior to 88.0.4324.146 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 confidenceUse-after-free vulnerability in Chrome's Navigation component prior to version 88.0.4324.146 allows a remote attacker with a compromised renderer process to potentially escape the sandbox via a specially 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
< 88.0.4324.146
FedoraOperating system
= 32= 33CVSS 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 Chrome versionNavigate to chrome://version in the Chrome browser or run 'google-chrome --version' from command lineAffected if The version shown is below 88.0.4324.146
-
Check Chrome package version on FedoraRun 'rpm -qa | grep google-chrome' to list the installed Chrome package, then check the version with 'rpm -q --qf '%{VERSION}-%{RELEASE} ' google-chrome-stable'Affected if On Fedora 32 or 33, the installed Chrome package version is earlier than 88.0.4324.146
-
Verify if Navigation feature is in useThis vulnerability affects the Navigation component which is active during page navigation in Chrome. The issue requires a compromised renderer process, which cannot be directly detected without examining crash dumps or memory traces after visiting untrusted pagesAffected if A compromised renderer process combined with a specially crafted HTML page triggers the use-after-free; the vulnerability is present in all Chrome versions below 88.0.4324.146 regardless of configuration
You are affected if Google Chrome version is below 88.0.4324.146, or if you are running Chrome on Fedora 32 or 33 with an older package version.
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.4324.146
Update Google Chrome to version 88.0.4324.146 or later to patch the vulnerability.
Chrome 88.0.4324.146 or later
- Verify current Chrome version by navigating to chrome://settings/help
- Download and install Chrome version 88.0.4324.146 or later from the official Google Chrome release channel (google.com/chrome)
- Restart the Chrome browser after installation to apply the update
- For Fedora systems: run 'sudo dnf update' to apply available security patches for the chromium package
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
- 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 $1,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2021-21146 — 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-21146 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