CVE-2016-5132

CVE-2016-5132 is a high-severity vulnerability in Google Chrome with a CVSS 3.x base score of 8.8. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-254.

Key facts

Description

The Service Workers subsystem in Google Chrome before 52.0.2743.82 does not properly implement the Secure Contexts specification during decisions about whether to control a subframe, which allows remote attackers to bypass the Same Origin Policy via an https IFRAME element inside an http IFRAME element.

Frequently asked questions

What is CVE-2016-5132?
The Service Workers subsystem in Google Chrome before 52.0.2743.82 does not properly implement the Secure Contexts specification during decisions about whether to control a subframe, which allows remote attackers to bypass the Same Origin Policy via an https IFRAME element inside an http IFRAME element.
How severe is CVE-2016-5132?
CVE-2016-5132 has a CVSS 3.x base score of 8.8, rated high severity. It is exploitable over network with low attack complexity, requires no privileges and user interaction. Impact on confidentiality is high, integrity high, and availability high.
Is CVE-2016-5132 being actively exploited?
It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 1% (71st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2016-5132?
CVE-2016-5132 affects Google Chrome. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2016-5132?
Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround. Given its high severity, prioritise patching exposed systems.
When was CVE-2016-5132 published?
CVE-2016-5132 was published on 2016-07-23 and last updated on 2026-06-17.

References

Affected products (1)

More vulnerabilities in Google Chrome

All CVEs affecting Google Chrome →

Other CWE-254 vulnerabilities

Browse all CWE-254 vulnerabilities →