CVE-2016-1636

What it is

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.

At a glance

Exploitability

Can be exploited over the network without logging in. High risk of data exposure, data tampering, service disruption.

Exploit odds

1.8% chance of exploitation in the next 30 days (EPSS).

Fix

No patch or advisory is linked yet. Look at mitigations or restrict exposure.

Timeline

1. 2016-01-12 00:00 UTC ReservedThe CVE id was reserved by its CNA
2. 2016-03-06 02:59 UTC PublishedDisclosed publicly on CVE.org and NVD
3. 2026-06-17 00:42 UTC Last updatedMost recent change to the record

Why it ranks here

• Exploited in the wild: no, CISA does not list it.
• Exploit odds: 1.8% in the next 30 days (EPSS).
• Severity: 9.8 CRITICAL (CVSS).
• Fix: none linked yet, which raises it.

Details

Published

2016-03-06 02:59 UTC

Last modified

2026-06-17 00:42 UTC

Exploit probability

1.8% · EPSS, next 30 days

Weakness

CWE-264

Record status

Modified

Affected

• Google Chrome ≤ 48.0.2564.116

Attack profile CVSS 3.0 · 9.8

Attack vector

Network

Complexity

Low

Privileges needed

None

User interaction

None

Scope

Unchanged

Confidentiality

High

Integrity

High

Availability

High

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2016-1636.md and follow it. Check whether this project is affected by CVE-2016-1636. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

Copy as ticket · More options · Status badge