ChromeWeb browser · Google
CVE-2020-16009
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 V8 in Google Chrome prior to 86.0.4240.183 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 confidenceA heap corruption vulnerability exists in the V8 JavaScript engine of Google Chrome versions prior to 86.0.4240.183. The inappropriate implementation allows a remote attacker to exploit memory corruption via a specially crafted HTML page, potentially leading to arbitrary code execution.
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
< 86.0.4240.183
FedoraOperating system
= 32= 33
Debian LinuxOperating system
= 10.0< 86.0.241< 86.0.622.63< 86.0.4240.183= 15.0= 15.1= 15.2CVSS 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 checksWork through these to decide whether this CVE applies to you.
-
Check Google Chrome versionNavigate to chrome://settings/help or run 'google-chrome --version' in command lineAffected if Version number is less than 86.0.4240.183
-
Check Microsoft Edge versionNavigate to edge://settings/help or run 'msedge --version' in command lineAffected if Version number is less than 86.0.622.63 (legacy) or less than 86.0.4240.183 (Chromium-based)
-
Check CefSharp version if embeddedInspect the CefSharp assembly version or check the NuGet package reference in the projectAffected if Version number is less than 86.0.241
-
Check browser JavaScript executionVerify that JavaScript is enabled in the browser settings (default state). This vulnerability is triggered when processing malicious JavaScript.Affected if JavaScript is enabled and a crafted HTML page is loaded (user interaction required)
You are affected if any installed browser (Chrome, Edge, or CefSharp) has a version lower than the thresholds listed, and a user can be tricked into opening a malicious HTML page with JavaScript.
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 · scoped86.0.24186.0.622.6386.0.4240.183
Update Google Chrome to version 86.0.4240.183 or later to patch the V8 engine vulnerability. Organizations should deploy the update through their patch management infrastructure and verify complete coverage across all endpoints.
Chrome/Edge Chromium 86.0.4240.183 or later; CefSharp 86.0.241 or later
- Upgrade Google Chrome to version 86.0.4240.183 or later
- If using Microsoft Edge Chromium, upgrade to version 86.0.4240.183 or later
- If using CefSharp, upgrade to version 86.0.241 or later
- For Fedora systems, apply available system updates
- For Debian 10.0, apply security updates
- For SUSE Leap 15.1/15.2 and SUSE Linux Enterprise, apply available patches
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
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 locallyCheck whether your project pulls in CVE-2020-16009 — 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-2020-16009 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