Chrome 148 · Version Status
Chrome 148 End of Life Date
Chrome 148 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚡
Chrome 148 reaches end of life on June 5, 2026. Plan your migration now — 27 days remaining.
EOL Date
Jun 5, 2026
27 days remaining
Latest Release
—
Standard release
Release Date
May 5, 2026
Chrome 148 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 148 end of life mean?
When Chrome 148 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 148 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to a supported version or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Chrome 148 reach end of life?
Chrome 148 reached end of life on June 5, 2026. That is 27 days remaining.
Is Chrome 148 still supported?
Chrome 148 is still supported but approaching end of life on June 5, 2026. Begin planning your migration now.
What should I upgrade to from Chrome 148?
What are the security risks of running Chrome 148 past EOL?
When Chrome 148 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.