Free and open · new CVEs checked every 20 minutesStatusRSSOpen dataContact

CVE-2016-5128: objects.cc in Google V8 before 5.2.361.27, as used in Google Chrome before 52.0.2743.82, does not prevent API

48
This month
HIGH 8.8UPGRADEDOWNGRADE

CVE-2016-5128 is a high-severity flaw (CVSS 8.8) affecting chrome, v8. Below: why it ranks where it does, which versions are affected, what to do, and the exact commands.

objects.cc in Google V8 before 5.2.361.27, as used in Google Chrome before 52.0.2743.82, does not prevent API interceptors from modifying a store target without setting a property, which allows remote attackers to bypass the Same Origin Policy via a crafted web site.

Why this priority

  • High severity

A fixed release or distro patch exists.

Risk facts

CVSS score8.8 (High)
Attack vectorNetwork (remote)
Attack complexityLow
Privileges neededNone
User interactionRequired
EPSS exploit chance1.3% (top 30%)
CISA exploited listNo
WeaknessCWE-254
Published2016-07-23
Last modified2026-06-17
Publisher (CNA): Chrome · Vendor: google

Share: LinkedIn · X · Reddit

Last updated 2026-06-17 · Sources: CVE Program, NVD, CISA KEV, EPSS and vendor advisories · How we score

Am I affected?

Timeline

google chrome UPGRADE
Affected: <= 51.0.2704.106
Fixed in: newer than 51.0.2704.106
Safe to downgrade to: no unaffected older release
1. Check installed version
apt-cache policy chrome || rpm -q chrome || chrome --version
2. UPGRADE to newer than 51.0.2704.106 (Debian / Ubuntu)
sudo apt update && sudo apt install --only-upgrade chrome
2. UPGRADE (RHEL / Amazon Linux / Fedora)
sudo dnf upgrade chrome
Note
Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.
google v8 DOWNGRADE
Affected: 5.2.360
Fixed in: no fixed release known
Safe to downgrade to: a release before 5.2.360
1. Check installed version
apt-cache policy v8 || rpm -q v8 || v8 --version
2. No fixed release: DOWNGRADE to a release before 5.2.360 (Debian / Ubuntu)
apt-cache madison v8 sudo apt install v8=<VERSION_BEFORE_5.2.360> sudo apt-mark hold v8
2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)
dnf --showduplicates list v8 sudo dnf downgrade v8-<VERSION_BEFORE_5.2.360> sudo dnf versionlock add v8
Downgrade risk
Downgrading can break dependent software and may reopen older bugs. Read the distro advisory first and test on a non-production host.
After downgrade
Restart the service, and keep the package held until a fixed release ships.
Verify at the official source NVD · CVE Program · Report a problem with this page
Scores and fixes here are computed automatically from those and other public sources. Confirm with the vendor advisory before changing production systems.

Quick answers

How do I fix CVE-2016-5128?

chrome: upgrade to newer than 51.0.2704.106; v8: downgrade or apply the listed mitigation. Exact commands for each OS are on this page.

Is CVE-2016-5128 being exploited?

CVE-2016-5128 is not on the CISA Known Exploited Vulnerabilities list at the time of the last update. Check again, as this can change.

What does CVE-2016-5128 affect?

CVE-2016-5128 affects chrome, v8. Severity is high (CVSS 8.8). objects.cc in Google V8 before 5.2.361.27, as used in Google Chrome before 52.0.2743.82, does not prevent API interceptors from modifying a store target without setting a property, which allows remote attackers to bypass the Same Origin Pol

How urgent is CVE-2016-5128?

Priority 48/100. High severity

Software pages

Google Chrome vulnerabilities

Related CVEs

References

← Back to latest CVEs

Get the weekly exploited-CVE digest by emailThe CVEs being attacked this week and how to fix them. No spam, unsubscribe any time.