VDB

CVE-2017-5027

CVE-2017-5027 PUBLISHED

Reported by chrome · Published February 17, 2017

Blink in Google Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android, failed to properly enforce unsafe-inline content security policy, which allowed a remote attacker to bypass content security policy via a crafted HTML page.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
oxide-qtUbuntu:14.04:LTS1.20.4-0ubuntu0.14.04.1
chromium-browserUbuntu:16.04:LTS56.0.2924.76-0ubuntu0.16.04.1268
chromegoogle55.0.2883.87

Affected products

VendorProductVersions
n/aGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for AndroidGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android
n/aGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for AndroidGoogle Chrome prior to 56.0.2924.76 for Linux, Windows and Mac, and 56.0.2924.87 for Android

Timeline

  • Feb 17, 2017 CVE Published
  • Apr 14, 2021 EPSS Score (30 in total, the first dated here)
  • Apr 20, 2025 CVE Updated
  • Apr 7, 2026 Security Advisory
  • Sep 29, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2017-5027
vulnetix vdb fixes CVE-2017-5027

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2017-5027/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

  • x_refsource_CONFIRM
  • x_refsource_CONFIRM
Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›