Chrome 51 · Version Status

Chrome 51 End of Life Date

Chrome 51 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

Chrome 51 is past end of life. This version no longer receives security patches. 3581 days past EOL — migrate to a supported version immediately.
EOL Date
Jul 19, 2016
3581 days past EOL
Latest Release
Standard release
Release Date
May 24, 2016
Chrome 51 series
← Chrome 50 All Chrome versions Chrome 52 →
Recommended upgrade path
Chrome 147
Latest release: — · EOL: Supported
View full Chrome timeline →
All Chrome Versions
VersionLatestEOL DateStatus
7 Nov 30, 2010 EOL
8 Jan 25, 2011 EOL
9 Mar 8, 2011 EOL
10 Apr 19, 2011 EOL
11 May 31, 2011 EOL
12 Jul 26, 2011 EOL
13 Sep 6, 2011 EOL
14 Oct 18, 2011 EOL

What does Chrome 51 end of life mean?

When Chrome 51 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.

The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Chrome 51 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.

Migrate to Chrome 147 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.

Frequently Asked Questions
When does Chrome 51 reach end of life?
Chrome 51 reached end of life on July 19, 2016. This version is no longer receiving security patches.
Is Chrome 51 still supported?
No. Chrome 51 reached end of life on July 19, 2016 and is no longer receiving security patches.
What should I upgrade to from Chrome 51?
The recommended upgrade from Chrome 51 is Chrome 147 — the latest actively supported version. Check the Chrome full timeline for all supported versions.
What are the security risks of running Chrome 51 past EOL?
When Chrome 51 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Chrome should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →