ChromeWeb browser · Google
CVE-2016-5190
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 · uneditedGoogle Chrome prior to 54.0.2840.59 for Windows, Mac, and Linux; 54.0.2840.85 for Android incorrectly handled object lifecycles during shutdown, which allowed a remote attacker to perform an out of bounds memory read via crafted HTML pages.
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 confidenceGoogle Chrome had a memory safety vulnerability in its object lifecycle handling during shutdown. When the browser was closing, certain objects were not properly managed, allowing a crafted HTML page to trigger an out-of-bounds memory read. This could potentially expose sensitive memory contents to a remote attacker.
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
<= 53.0.2785.143CVSS 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
- Low
- Integrity
- Low
- Availability
- Low
CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:L/I:L/A:L
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.
-
Verify Chrome is installedCheck for Chrome executable: On Windows, look in Program Files\Google\Chrome\Application\chrome.exe. On Mac, look in /Applications/Google Chrome.app. On Linux, run which google-chrome or find /usr -name 'google-chrome*'.Affected if Chrome is not installed on the system
-
Retrieve Chrome version numberOpen Chrome, click the three-dot menu (top right), select Help, then About Google Chrome. The version is displayed on that page. Alternatively, from command line: chrome --version (Windows/Mac) or google-chrome --version (Linux).Affected if Cannot determine version or Chrome is not accessible
-
Compare installed version against affected rangeThe affected version range is any Chrome version <= 53.0.2785.143. Compare your installed version number to this threshold. For example, if your version is 53.0.2785.143 or lower, you are in the affected range.Affected if Installed version is 53.0.2785.143 or lower (versions 54.0.2840.59 and later are fixed)
-
Confirm platform matches affected platformsVerify the Chrome installation is for desktop (Windows, Mac, Linux) or Android. This vulnerability affects Chrome on those platforms.Affected if Chrome is installed on a non-affected platform (e.g., iOS uses a different engine)
If Chrome is installed and the version is 53.0.2785.143 or lower, your environment is affected by this vulnerability.
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.
From vendor dataUpdate Google Chrome to version 54.0.2840.59 or later for desktop platforms, or 54.0.2840.85 for Android. Organizations should deploy browser updates through their patch management systems.
Fix this in Chrome
Scoped from the published advisory
- Consultation1.0 h
- Implementation2.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,424.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5190 — 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-2016-5190 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