CVE-2016-1706

Name: CVE-2016-1706
Creator: NVD / NIST
Published: 2016-07-23T19:59:01.59+00:00
License: https://creativecommons.org/publicdomain/zero/1.0/

UnknownEPSS 2.43%

Last modified Jun 17, 2026

CVE-2016-1706 is a vulnerability of currently unknown severity. The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.. EPSS estimates a 2.43% chance of exploitation in the next 30 days.

Description

The PPAPI implementation in Google Chrome before 52.0.2743.82 does not validate the origin of IPC messages to the plugin broker process that should have come from the browser process, which allows remote attackers to bypass a sandbox protection mechanism via an unexpected message type, related to broker_process_dispatcher.cc, ppapi_plugin_process_host.cc, ppapi_thread.cc, and render_frame_message_filter.cc.

Metrics

EPSS Probability

2.43%

82.1th percentile

Probability of exploitation in the next 30 days. Learn more

Weakness Enumeration

CWE-20

Affected Software

Vendor	Product	Versions
Google	Chrome	<= 51.0.2704.106

References

Timeline

Published: Jul 23, 2016
Last Modified: Jun 17, 2026
Status: Modified

Frequently Asked Questions

What is CVE-2016-1706?

How severe is CVE-2016-1706?

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

How do I fix CVE-2016-1706?

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-1706?

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

Scan your code now

Source: NVD / NIST