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