ChromeWeb browser · Google
CVE-2020-16010
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 · uneditedHeap buffer overflow in UI in Google Chrome on Android prior to 86.0.4240.185 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 confidenceHeap buffer overflow vulnerability in the UI component of Google Chrome on Android prior to version 86.0.4240.185. A remote attacker with an already compromised renderer process could exploit this via a crafted HTML page to potentially escape the sandbox and execute arbitrary code.
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.185CVSS 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.
-
Identify if Google Chrome for Android is installedCheck the list of installed applications on the Android device. Navigate to Settings > Apps and look for Google Chrome in the app list.Affected if Google Chrome for Android is present on the device
-
Determine the installed version of Google ChromeOpen Google Chrome, tap the three-dot menu, go to Settings > About Chrome. The version number is displayed on this page.Affected if The displayed version number is less than 86.0.4240.185 (for example, 86.0.4240.111 or earlier)
-
Verify the attack surface existsConfirm that Chrome is used as the default browser or that users access untrusted web content. This vulnerability is in the UI component and is triggered when the renderer process has already been compromised.Affected if Chrome processes untrusted web content and the device runs an affected version
A device is affected if Google Chrome for Android is installed with a version number lower than 86.0.4240.185 and the device accesses web content, since exploitation requires a compromised renderer process which can be triggered through crafted HTML pages.
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.4240.185
Update Google Chrome for Android to version 86.0.4240.185 or later. Organizations should leverage mobile device management (MDM) to enforce Chrome updates or verify compliance across managed devices.
Chrome 86.0.4240.185 or later for Android
- Open Google Play Store on the Android device
- Search for Google Chrome
- If an update is available, tap 'Update' to install Chrome version 86.0.4240.185 or later
- Alternatively, go to Settings > Apps > Google Chrome > Updates to check for and install updates
- Restart the browser after the update completes
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
- Implementation4.0 h
- Testing3.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,800.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2020-16010 — 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-16010 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