Chrome 35 · Version Status
Chrome 35 End of Life Date
Chrome 35 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Chrome 35 is past end of life. This version no longer receives security patches. 4337 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 24, 2014
4337 days past EOL
Latest Release
—
Standard release
Release Date
May 13, 2014
Chrome 35 series
| Version | Latest | EOL Date | Status |
|---|
| 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 35 end of life mean?
When Chrome 35 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 35 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 35 reach end of life?
Chrome 35 reached end of life on June 24, 2014. This version is no longer receiving security patches.
Is Chrome 35 still supported?
No. Chrome 35 reached end of life on June 24, 2014 and is no longer receiving security patches.
What should I upgrade to from Chrome 35?
The recommended upgrade from Chrome 35 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 35 past EOL?
When Chrome 35 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.