ChromeWeb browser · Google
CVE-2016-5219
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 · uneditedA heap use after free in V8 in Google Chrome prior to 55.0.2883.75 for Mac, Windows and Linux, and 55.0.2883.84 for Android 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 use-after-free vulnerability in the V8 JavaScript engine in Google Chrome versions prior to 55.0.2883.75 (desktop) and 55.0.2883.84 (Android) allows remote attackers to potentially exploit heap corruption via a specially crafted HTML page. The vulnerability occurs when freed memory is accessed after being deallocated, leading to unpredictable behavior and potential 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
<= 54.0.2840.99CVSS 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.
-
Check the installed Google Chrome version on desktopOpen Google Chrome, click the three-dot menu in the top-right corner, select 'Help', then 'About Google Chrome'. The version number will be displayed on the page that opens.Affected if The displayed version is 54.0.2840.99 or earlier (any version below 55.0.2883.75)
-
Check the installed Google Chrome version on AndroidOpen the Google Chrome app on Android, tap the three-dot menu, select 'Settings', then 'About Chrome' to view the version number.Affected if The displayed version is 55.0.2883.83 or earlier (any version below 55.0.2883.84)
-
Verify if V8 JavaScript engine is enabledThis is not applicable to check separately. The V8 JavaScript engine is built into Google Chrome and cannot be disabled. It is always active when Chrome is running.Affected if V8 is always enabled in Google Chrome by default, so this condition is always true for any Chrome installation
You are affected if you are running Google Chrome version 54.0.2840.99 or earlier on desktop, or version 55.0.2883.83 or earlier on Android, as the heap use-after-free vulnerability in the V8 JavaScript engine is present in those versions.
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 55.0.2883.75 or later for desktop platforms, and 55.0.2883.84 or later for Android. Organizations should verify all endpoints have received the update through their patch management systems.
Fix this in Chrome
Scoped from the published advisory
- Consultation3.0 h
- Implementation6.0 h
- Testing3.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $3,984.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2016-5219 — 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-5219 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