CISA list

● Branch of Google Chrome

Google Chrome 143

Google Chrome 143 reached end of life on 13 January 2026 and gets no fixes. Move to 158.0.8127.36 or newer.

Data: .

Fix releases of Google Chrome 143

Releases that end an affected range of a CVE record, newest first. Records this page cannot place on a branch, counted on the page of the platform, are not in it.
ReleaseFixesSigns of exploitation
143.0.7499.1921 CVE record that this page readsnone among the records this page reads
143.0.7499.1472 CVE records that this page readsnone among the records this page reads
143.0.7499.1103 CVE records that this page reads1 record on CISA's list (CVE-2025-14174) among the records this page reads
143.0.7499.4113 CVE records that this page readsnone among the records this page reads

Google Chrome 143 in dates

WhatWhen
Released2 December 2025
Security fixes end13 January 2026
Newest release143.0.7499.192

What this page says

This page reads 4,173 CVE records that Google Chrome's CVE Numbering Authority has published since 13 January 2026 and that name Google Chrome. None of them gives a range of its own for Google Chrome 143. 4,173 records give a range with no start that ends in a newer branch; as the record states it, that range covers Google Chrome 143 too.

No release of Google Chrome 143 is called safe here, because the branch has ended, whatever the records say of it.

The lifecycle data does not list 158.0.8127.36: 203 CVE records name it as a fix.

A release is the fix of a record when the record's affected range for this branch ends before it. Dates are from the product lifecycle data credited under Sources.

Sources
  • CVE records: Copyright © 1999-2026, The MITRE Corporation. CVE is a trademark and the CVE logo is a registered trademark of The MITRE Corporation (source). Licence: CVE Program Terms of Use
  • Product lifecycle dates from endoflife.date, Copyright 2020 endoflife.date contributors (MIT License) (source). Licence: MIT License
  • EPSS scores by FIRST (https://www.first.org/epss/), generated by Empirical Security (source)