Chrome 132.x — End of Life

EOL
EOL: Feb 4, 20251 release in this series0 CVEs

Chrome 132.x — All releases

VersionReleasedActive supportEOL dateLatest patchStatus
132Jan 14, 2025Feb 4, 2025EOL

CVEs affecting Chrome 132.x (0)

No CVEs tracked for Chrome 132.x.

Chrome 132.x is EOL — migrate to Chrome 133.x

Chrome 133.x is the next major release. Plan your upgrade before Chrome 132.x stops receiving security patches.

See Chrome 133.x

Frequently asked questions

Is Chrome 132 end of life?

Yes. All Chrome 132.x releases have reached end of life and no longer receive security patches. Migrate to Chrome 133.x as soon as possible.

What CVEs affect Chrome 132?

No CVEs are currently tracked for Chrome 132.x in our database. This may mean no vulnerabilities have been recorded yet, or the data is still syncing.

What is the latest Chrome 132 version?

Check the version table above for the latest Chrome 132.x patch release.

How to migrate from Chrome 132 to Chrome 133?

To migrate from Chrome 132 to Chrome 133: (1) review the official Chrome 133 migration guide for breaking changes, (2) update dependencies and configuration accordingly, (3) test thoroughly in a staging environment, (4) deploy with a rollback plan. Starting early gives you time to resolve compatibility issues before your current version reaches end of life.

Is it safe to run Chrome 132 in production?

No. Chrome 132 has reached end of life and security vulnerabilities are no longer patched. Upgrade to a supported version immediately.

Data sourced from endoflife.date · CVE data from NVD · EPSS from FIRST.org · KEV from CISA