● Branch of Google Chrome
Google Chrome 62
Google Chrome 62 reached end of life on 5 December 2017 and gets no fixes. Move to 158.0.8127.36 or newer.
Data: .
Fix releases of Google Chrome 62
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 62.0.3202.94 | 1 CVE record that this page reads | none among the records this page reads |
| 62.0.3202.74 | 1 CVE record that this page reads | none among the records this page reads |
| 62.0.3202.62 | 1 CVE record that this page reads | none among the records this page reads |
Google Chrome 62 in dates
| What | When |
|---|---|
| Released | 17 October 2017 |
| Security fixes end | 5 December 2017 |
| Newest release | 62.0.3202.94 |
What this page says
This page reads 6,359 CVE records that Google Chrome's CVE Numbering Authority has published since 5 December 2017 and that name Google Chrome. 26 of them are not placed on a branch (the page of the platform counts why). Of the others, 3 give a range of its own for Google Chrome 62, and 6,320 give a range with no start that ends in a newer branch; as the record states it, that range covers Google Chrome 62 too.
No release of Google Chrome 62 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)