● Branch of Google Chrome
Google Chrome 136
Google Chrome 136 reached end of life on 27 May 2025 and gets no fixes. Move to 158.0.8127.36 or newer.
Data: .
Fix releases of Google Chrome 136
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 136.0.7103.113 | 2 CVE records that this page reads | none among the records this page reads |
| 136.0.7103.92 | 1 CVE record that this page reads | none among the records this page reads |
| 136.0.7103.59 | 6 CVE records that this page reads | none among the records this page reads |
Google Chrome 136 in dates
| What | When |
|---|---|
| Released | 29 April 2025 |
| Security fixes end | 27 May 2025 |
| Newest release | 136.0.7103.113 |
What this page says
This page reads 4,311 CVE records that Google Chrome's CVE Numbering Authority has published since 27 May 2025 and that name Google Chrome. 3 records give a range of its own for Google Chrome 136. 4,300 records give a range with no start that ends in a newer branch; as the record states it, that range covers Google Chrome 136 too.
No release of Google Chrome 136 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)