CVE-2016-5129: Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trim

Q: How do I fix CVE-2016-5129?

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

Q: Is CVE-2016-5129 being exploited?

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

Q: What does CVE-2016-5129 affect?

CVE-2016-5129 affects chrome, v8. Severity is high (CVSS 8.8). Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other imp

This month

HIGH 8.8DOWNGRADEUPGRADE

CVE-2016-5129 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.

Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other impact via crafted JavaScript code.

Why this priority

High severity

A fixed release or distro patch exists.

Risk facts

CVSS score	8.8 (High)
Attack vector	Network (remote)
Attack complexity	Low
Privileges needed	None
User interaction	Required
EPSS exploit chance	2.1% (top 18%)
CISA exploited list	No
Weakness	CWE-119
Published	2016-07-23
Last modified	2026-06-17

Publisher (CNA): Chrome · Vendor: google

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

Am I affected?

Timeline

2016-07-23 19:59 UTCPublished CVE record published
2026-06-17 00:48 UTCUpdated Record last modified

google chrome DOWNGRADE

Affected: 51.0.2704.106

Fixed in: no fixed release known

Safe to downgrade to: a release before 51.0.2704.106

1. Check installed version

apt-cache policy chrome || rpm -q chrome || chrome --version

2. No fixed release: DOWNGRADE to a release before 51.0.2704.106 (Debian / Ubuntu)

apt-cache madison chrome sudo apt install chrome=<VERSION_BEFORE_51.0.2704.106> sudo apt-mark hold chrome

2. No fixed release: DOWNGRADE (RHEL / Amazon Linux / Fedora)

dnf --showduplicates list chrome sudo dnf downgrade chrome-<VERSION_BEFORE_51.0.2704.106> sudo dnf versionlock add chrome

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.

google v8 UPGRADE

Affected: <= 5.2.360

Fixed in: newer than 5.2.360

Safe to downgrade to: no unaffected older release

1. Check installed version

apt-cache policy v8 || rpm -q v8 || v8 --version

2. UPGRADE to newer than 5.2.360 (Debian / Ubuntu)

sudo apt update && sudo apt install --only-upgrade v8

2. UPGRADE (RHEL / Amazon Linux / Fedora)

sudo dnf upgrade v8

Note

Distros often backport fixes without changing the version number. Confirm with the distro advisory or changelog.

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

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

Is CVE-2016-5129 being exploited?

CVE-2016-5129 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-5129 affect?

CVE-2016-5129 affects chrome, v8. Severity is high (CVSS 8.8). Google V8 before 5.2.361.32, as used in Google Chrome before 52.0.2743.82, does not properly process left-trimmed objects, which allows remote attackers to cause a denial of service (memory corruption) or possibly have unspecified other imp

How urgent is CVE-2016-5129?

Priority 51/100. High severity

Software pages

Google Chrome vulnerabilities

Related CVEs

CVE-2026-76031 HIGH 8.8 UPGRADE Use after free in Input in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbitrary
CVE-2026-76030 HIGH 8.8 UPGRADE Memory corruption in FileSystem in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potential
CVE-2026-76029 HIGH 8.8 UPGRADE Memory corruption in Network in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to potentially
CVE-2026-76028 HIGH 8.8 UPGRADE Use after free in FileSystem in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arbi
CVE-2026-76026 HIGH 8.8 UPGRADE Memory corruption in Autofill in Google Chrome prior to 156.0.8078.79 allowed a remote attacker to execute arb

References

← Back to latest CVEs