Skip to content
Fencer Vulns
medium 6.5

CVE-2016-5176 json

Google Chrome before 53.0.2785.113 allows remote attackers to bypass the SafeBrowsing protection mechanism via unspecified vectors.

published 2016-09-29 10 y ago modified 2026-06-17 4 mo ago also EUVD-2016-6127

cvss
6.5
version 3.0, NVD
cisa kev
Not listed
not in CISA's catalog
epss
0.8%
EPSS 0.8% chance of exploitation in 30 days, percentile 56%
public exploits
0
none known

Summary

Google Chrome before 53.0.2785.113 allows remote attackers to bypass the SafeBrowsing protection mechanism via unspecified vectors.

Patch / fix

  • chromium-browser Ubuntu 14.04 LTS 53.0.2785.143-0ubuntu0.14.04.1.1142
  • chromium-browser Ubuntu 16.04 LTS 53.0.2785.143-0ubuntu0.16.04.1.1254

ubuntu advisories UBUNTU-CVE-2016-5176

Ubuntu security data © Canonical Ltd., from https://github.com/canonical/ubuntu-security-notices via OSV; changed: normalised to fixed package versions per release. CC BY-SA 4.0

  • chromium-browser RHEL 6 EXTRAS 53.0.2785.113-1.el6

red hat advisories RHSA-2016:1905

Vendor advisories

What the vendors themselves say about their products: affected, fixed or not affected, and what to do.

red hat product security vex CVE-2016-5176 updated cvss 5.3

chromium-browser: SafeBrowsing protection mechanism bypass

  • Red Hat Enterprise Linux Desktop Supplementary (v. 6) chromium-browser 53.0.2785.113-1.el6 Red Hat Enterprise Linux Server Supplementary (v. 6) chromium-browser 53.0.2785.113-1.el6 Red Hat Enterprise Linux Workstation Supplementary (v. 6) chromium-browser 53.0.2785.113-1.el6
    fixed: vendor fix RHSA-2016:1905

Red Hat CSAF VEX © Red Hat, Inc., from https://security.access.redhat.com/data/csaf/v2/vex/; changed: reduced to product statuses and remediations. CC BY 4.0 · csaf

Exploit prediction

0.80% chance of exploitation in the next 30 days, higher than 56% of all scored CVEs (FIRST EPSS, 2026-11-08).

CVSS scores

assigned by version score vector
NVD 3.0 6.5 CVSS:3.0/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:H/A:N
NVD 2.0 4.3 AV:N/AC:M/Au:N/C:N/I:P/A:N

Classification

Weakness
Technology feeds

References

Sources

Fencer Vulns keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.