Google Chrome End of Life (EOL) Dates & Support Timeline

Google Chrome lifecycle status — the real story

Google ships a new Chrome major version every four weeks on the Stable channel, with minor security updates every two to three weeks in between. Each major is superseded — and stops receiving updates — when the next one arrives, which is why every line in the table above lives for roughly four weeks and the only supported version is the current one.

Organizations that cannot move every month can use the Extended Stable channel, updated every eight weeks while still receiving security fixes. On either channel there is no such thing as a long-term Chrome version: the security model is "always current".

Verified against the vendor's lifecycle documentation on August 22, 2026.

Google Chrome release and support pattern

Across the 147 release lines with a published release date, Google Chrome has shipped a new line roughly every 6 weeks (median interval). A line typically stays supported for about 6 weeks from its release to its end-of-life date.

Of the 147 release lines tracked, 146 are past end of life and 1 is still within support. The newest line, 154, was released September 22, 2026. The next scheduled end of life is 154 on October 6, 2026 — 10 days from this build.

Computed from the tracked release data at every build — the figures above are the dates in the table, restated, not an editorial estimate.

Google Chrome security intelligence

CISA KEV history: Google Chrome is named in CISA's Known Exploited Vulnerabilities catalog 71 times, most recently on 2026-09-09. Derived from CISA's live catalog at every build.

What does Google Chrome end of life mean for your organization?

When a version of Google Chrome reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.

The CVE blind spot: A CVE-based scan does not show the accumulation of unpatched vulnerabilities in EOL software. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no vendor patch is coming. This is one of the most dangerous gaps in enterprise security posture.

Organizations running EOL Google Chrome should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.

Your options when Google Chrome reaches end of life

There are four realistic paths. Which one is right depends far more on how long the system needs to keep running than on the version you are on today.

How to choose, in one question: how many more years does this system need to run? Under a year, extended support (where it exists) is usually cheaper than an emergency migration. One to three years, migrate — support purchased repeatedly costs more than doing the project once, and the project only gets harder as the version ages. Indefinitely, migrate now and plan the next migration before it surprises you.

Worth saying plainly, because vendors selling extended support rarely will: extended support is often the more expensive choice over a multi-year horizon. It is the right answer when a deadline is genuinely unreachable, not as a default. Compare the annual fee against the one-time cost of migrating before committing to either.

Related Products