VDB

CVE-2016-1636

CVE-2016-1636 PUBLISHED

Reported by chrome · Published March 6, 2016

The PendingScript::notifyFinished function in WebKit/Source/core/dom/PendingScript.cpp in Google Chrome before 49.0.2623.75 relies on memory-cache information about integrity-check occurrences instead of integrity-check successes, which allows remote attackers to bypass the Subresource Integrity (aka SRI) protection mechanism by triggering two loads of the same resource.

Fixed versions

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

PackageEcosystemFixed in
chromegoogle48.0.2564.116
oxide-qtUbuntu:14.04:LTS1.13.6-0ubuntu0.14.04.1

Affected products

VendorProductVersions
n/an/an/a
n/an/a*

Timeline

  • Mar 3, 2016 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Aug 5, 2024 CVE Updated
  • Mar 5, 2026 Distribution Patch (3 in total, the first dated here)
  • Mar 5, 2026 Security Advisory (8 in total, the first dated here)
  • Oct 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-1636
vulnetix vdb fixes CVE-2016-1636

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-2016-1636/fixes/registry"

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

References

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