Google Chrome 157 · Version Status

Google Chrome 157 End of Life Date

Google Chrome 157 end-of-life date, support status, and CVE risk. Data reconciled from official vendor documentation and endoflife.date at every build; the source of each date is on the product page.

⚡ Google Chrome 157 reaches end of life on November 17, 2026. Plan your migration now — 11 days remaining.
📅 Get reminded before Google Chrome 157 reaches EOL on November 17, 2026 — alerts 90, 30 & 7 days out.
Google →
✉️ Or get it by email — alerts at 90 / 60 / 30 / 7 days and on the day: Free · one-click unsubscribe in every email · no other mail, ever
EOL Date
Nov 17, 2026
11 days remaining
Latest Release
—
Standard release
Release Date
Nov 3, 2026
Google Chrome 157 series
Where these dates come from
End of lifeNov 17, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
ReleaseNov 3, 2026endoflife.date (open dataset) · endoflife.datemedium · 1 source agrees
Confidence: high = two or more independent sources agree (the vendor's page read by our adapter, a person's check against the vendor, the dataset the date came from); medium = one; low = the vendor page disagrees or our last read is stale. How we source dates.
Spotted a date that disagrees with the vendor's own lifecycle page? Report it with the vendor's link → Every correction is published on the accuracy page.
Lifecycle detail

Google Chrome 157 was released on November 3, 2026 and support is scheduled to end on November 17, 2026 — a planned supported lifespan of 14 days, shorter than the 42 days median for Google Chrome releases.

← Google Chrome 156 All Google Chrome versions
55 / 100
High Risk
EOL Risk Score™  How is this calculated? →
EOL Recency
15/40
Attack Surface
10/30 Medium tier
CISA KEV Exposure
20/20 Named in CISA 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 157 end of life mean?

When Google Chrome 157 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: A CVE-based scan does not show the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Some scanners flag unsupported versions of common products, but coverage varies, and none of them give you the date in advance. Running Google Chrome 157 past its EOL date creates a growing attack surface that a clean scan result does not rule out.

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 157 reach end of life?
Google Chrome 157 reaches end of life on November 17, 2026. That is 11 days remaining.
Is Google Chrome 157 still supported?
Google Chrome 157 is still supported but approaching end of life on November 17, 2026. Begin planning your migration now.
What should I upgrade to from Google Chrome 157?
Check the Google Chrome full timeline for currently supported versions.
What are the security risks of running Google Chrome 157 past EOL?
When Google Chrome 157 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no vendor fix. A CVE-based scan does not show this — it is the CVE blind spot; some scanners flag unsupported versions of common products, but coverage varies and none give the date in advance. 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 →