dbcve.org
ChromeWeb browser · Google

CVE-2016-5192

MEDIUM · 6.5 CVSS v3.0 Published 2016-12-18
Fix available
A fix is available. Upgrade to after 53.0.2785.143 or later.
See remediation →
72/100
Remediation priority · Elevated
Remotely reachable No privileges

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 · unedited
Blink in Google Chrome prior to 54.0.2840.59 for Windows missed a CORS check on redirect in TextTrackLoader, which allowed a remote attacker to bypass cross-origin restrictions 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 confidence

This is a CORS (Cross-Origin Resource Sharing) bypass vulnerability in Google's Blink rendering engine. The TextTrackLoader component failed to perform proper CORS validation when handling redirects, allowing attackers to bypass cross-origin restrictions and potentially access sensitive resources from other domains through crafted HTML pages.

MitigationUpdate Google Chrome to version 54.0.2840.59 or later to receive the vendor patch. Ensure browser auto-updates are enabled or deploy the update via enterprise software distribution.

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
Affected:<= 53.0.2785.143

CVSS 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
None
Integrity
High
Availability
None

CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N

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 checks

Work through these to decide whether this CVE applies to you.

  1. Confirm Google Chrome is installed
    On Windows: Check for chrome.exe in Program Files or Program Files (x86). On macOS: Check /Applications/Google Chrome.app. On Linux: Run 'which google-chrome' or check /usr/bin/google-chrome
    Affected if Google Chrome browser is present on the system
  2. Retrieve installed Chrome version
    Open Chrome, click the three-dot menu > Help > About Google Chrome, or navigate to chrome://settings/help. Alternatively, run 'google-chrome --version' on Linux/macOS or check the executable properties on Windows
    Affected if Unable to determine version - Chrome may be installed but version cannot be verified
  3. Compare version against affected range
    Compare the displayed version number to 53.0.2785.143. The affected version range is any version less than or equal to 53.0.2785.143
    Affected if Installed version is 53.0.2785.143 or lower (for example, 53.0.2785.92, 52.0.2743.x, etc.)

The environment is affected if Google Chrome is installed and the installed version is 53.0.2785.143 or any earlier version.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 data
Upgrade available Upgrade to a release after 53.0.2785.143
Interim mitigation

Update Google Chrome to version 54.0.2840.59 or later to receive the vendor patch. Ensure browser auto-updates are enabled or deploy the update via enterprise software distribution.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-5192 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-5192 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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