VDB

CVE-2016-1706

CVE-2016-1706 PUBLISHED

Reported by chrome · Published July 23, 2016

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.

Fixed versions

Upgrade to a fixed version or later. Language registries are listed first, then Linux distributions, then vendor products.

PackageEcosystemFixed in
chromegoogle51.0.2704.106

Affected products

VendorProductVersions
n/an/an/a
n/an/a*

Timeline

  • Jul 21, 2016 CVE Published
  • Feb 4, 2022 EPSS Score (30 in total, the first dated here)
  • Sep 8, 2025 CVE Updated
  • Mar 5, 2026 Distribution Patch (3 in total, the first dated here)
  • Mar 5, 2026 Security Advisory (9 in total, the first dated here)
  • Oct 9, 2026 Coalition ESS Score

Query this with the API

The same record, from the CLI:

vulnetix vdb vuln CVE-2016-1706
vulnetix vdb fixes CVE-2016-1706

Or with curl, using the org id and key from your account page:

curl -s -H "Authorization: ApiKey ${VULNETIX_ORG_ID}:${VULNETIX_API_KEY}" \
  "https://api.vdb.vulnetix.com/v2/vuln/CVE-2016-1706/fixes/registry"

The Community plan is free and allows 50 queries a day. Get a free API key · API quickstart

References

Look up in the Resolve Platform →
$ Lookup Community · 50/day Open Lookup ›