Google Chrome 132 · Version Status

Google Chrome 132 End of Life Date

Google Chrome 132 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.

⚠ Google Chrome 132 is past end of life. This version no longer receives security patches. 504 days past EOL — migrate to a supported version immediately.
EOL Date
Feb 4, 2025
504 days past EOL
Latest Release
—
Standard release
Release Date
Jan 14, 2025
Google Chrome 132 series
← Google Chrome 131 All Google Chrome versions Google Chrome 133 →
55 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
35/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
0/20 Not in 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
VersionLatestEOL DateStatus
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 132 end of life mean?

When Google 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 Google Chrome 132 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 Google Chrome 132 reach end of life?
Google Chrome 132 reached end of life on February 4, 2025. This version is no longer receiving security patches.
Is Google Chrome 132 still supported?
No. Google Chrome 132 reached end of life on February 4, 2025 and is no longer receiving security patches.
What should I upgrade to from Google Chrome 132?
Check the Google Chrome full timeline for currently supported versions.
What are the security risks of running Google Chrome 132 past EOL?
When Google 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 Google Chrome should migrate immediately or implement compensating controls.
Data from endoflife.date API · Generated at build time · How we source data →