CVE-2016-1636

Name: CVE-2016-1636
Creator: NVD / NIST
Published: 2016-03-06T02:59:07.4+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 1.84%

Last modified Jun 17, 2026

CVE-2016-1636 is a vulnerability of currently unknown severity. 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.. EPSS estimates a 1.84% chance of exploitation in the next 30 days.

Description

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.

Metrics

EPSS Probability

1.84%

76.2th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-264

Affected Software

Vendor	Product	Versions
Google	Chrome	<= 48.0.2564.116

References

Timeline

Published: Mar 6, 2016
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-1636?

How severe is CVE-2016-1636?

Severity scoring for CVE-2016-1636 is pending analysis. The EPSS model estimates a 1.84% probability of exploitation in the next 30 days.

How do I fix CVE-2016-1636?

Check the vendor references and advisories linked above for patched versions and mitigation guidance. You can also run a Strix scan to test if your systems are affected.

Are you affected by CVE-2016-1636?

Run a free Strix scan to check your systems for this vulnerability.

Scan your code now

Source: NVD / NIST