Chrome 147 · Version Status
Chrome 147 End of Life Date
Chrome 147 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
✓
Chrome 147 is actively supported. EOL date: Already EOL.
EOL Date
Already EOL
Supported
Latest Release
—
Standard release
Release Date
Apr 7, 2026
Chrome 147 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 147 end of life mean?
When Chrome 147 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 147 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 147 reach end of life?
Chrome 147 has already reached end of life.
Is Chrome 147 still supported?
Yes, Chrome 147 is currently supported. The EOL date is Already EOL.
What should I upgrade to from Chrome 147?
The recommended upgrade from Chrome 147 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 147 past EOL?
When Chrome 147 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.