Google Chrome 35 · Version Status
Google Chrome 35 End of Life Date
Google Chrome 35 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.
⚠
Google Chrome 35 is past end of life. This version no longer receives security patches. 4519 days past EOL — migrate to a supported version immediately.
EOL Date
Jun 24, 2014
4519 days past EOL
Latest Release
—
Standard release
Release Date
May 13, 2014
Google Chrome 35 series
Where these dates come from
End of lifeJun 24, 2014Vendor's own page, read by our adapter · chromiumdash.appspot.com · checked Nov 6, 2026high · 2 sources agree ReleaseMay 13, 2014Vendor's own page, read by our adapter · chromiumdash.appspot.com · checked Nov 6, 2026high · 2 sources agree Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale.
How we source dates.
Lifecycle detail
Google Chrome 35 was released on May 13, 2014 and support ended on June 24, 2014 — a supported lifespan of 42 days, in line with the 42 days median for Google Chrome releases. It has been past its end-of-life date for 12 years and 5 months. 120 newer Google Chrome releases have shipped since.
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA KEV
Extended Support
10/10 None available
EOL Risk Score™ — proprietary methodology by endoflife.ai. Factors: EOL recency, attack surface breadth, CISA KEV catalog presence, extended support availability. Updated at every build.
Methodology → ·
View score card →
All Google Chrome Versions
| 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 Google Chrome 35 end of life mean?
When Google 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Google Chrome 35 past its EOL date creates a growing attack surface that a clean scan result does not rule out.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Google Chrome 35 reach end of life?
Google Chrome 35 reached end of life on June 24, 2014. This version is no longer receiving security patches.
Is Google Chrome 35 still supported?
No. Google Chrome 35 reached end of life on June 24, 2014 and is no longer receiving security patches.
What should I upgrade to from Google Chrome 35?
What are the security risks of running Google Chrome 35 past EOL?
Since Google Chrome 35 reached end of life, the maintainers no longer issue security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. Organizations running EOL Google Chrome should migrate immediately or implement compensating controls.