dbcve.org
ChromeWeb browser · Google

CVE-2016-1636

CRITICAL · 9.8 CVSS v3.0 Published 2016-03-06
Fix available
A fix is available. Upgrade to after 48.0.2564.116 or later.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

In Google Chrome before 49.0.2623.75, the PendingScript::notifyFinished function incorrectly uses memory-cache information about whether an integrity check occurred rather than whether it succeeded. This allows attackers to bypass Subresource Integrity (SRI) protection by triggering two loads of the same resource—the first load can be manipulated, and the second load bypasses the integrity check because the cache only records that a check happened, not that it passed.

MitigationUpdate Google Chrome to version 49.0.2623.75 or later to patch this SRI bypass vulnerability.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
ChromeWeb browser
Affected:<= 48.0.2564.116

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.0/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check installed Chrome version
    Open Chrome, click the menu icon (three dots), select Help > About Google Chrome. The version number is displayed on that page.
    Affected if The version is 48.0.2564.116 or lower (any version up to and including 48.0.2564.116)
  2. Confirm Subresource Integrity is in use
    Inspect web pages served to the browser and look for <script> or <link> tags containing the 'integrity' attribute (e.g., integrity="sha256-...").
    Affected if Any pages load resources with SRI integrity attributes, this is the protection the vulnerability allows bypassing
  3. Verify browser caching is enabled
    In Chrome, open Developer Tools (F12), go to the Network tab, and ensure 'Disable cache' is unchecked. Alternatively, check chrome://settings/ to confirm caching is not disabled.
    Affected if Caching is enabled, this is required for the memory-cache behavior that enables the bypass

You are affected if Chrome version is 48.0.2564.116 or lower and you use Subresource Integrity on any web pages loaded in that browser.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 48.0.2564.116
Interim mitigation

Update Google Chrome to version 49.0.2623.75 or later to patch this SRI bypass vulnerability.

Recommended fix High confidence

Chrome 49.0.2623.75 or later (ideally latest stable release)

  1. 1. Verify the current Chrome version by navigating to chrome://settings/help or clicking Help > About Google Chrome
  2. 2. Download the latest stable version of Google Chrome from the official website (google.com/chrome) or your organization's software distribution channel
  3. 3. Install the update, which will be version 49.0.2623.75 or later
  4. 4. Restart the browser to complete the installation
Caveat Browser updates typically have minimal breaking changes; however, some legacy extensions or web compatibility behaviors may change

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Chrome Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing2.0 h
  • Review / QA1.0 h
9.0 hours of engineering $1,600
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,560.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2016-1636 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2016-1636 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data