● Branch of Go
Go 1.6
Go 1.6 reached end of life on 16 February 2017 and gets no fixes. Move to 1.26.11 or newer.
Data: .
Fix releases of Go 1.6
| Release | Fixes | Signs of exploitation |
|---|---|---|
| 1.6.4 | 2 CVE records | none |
| 1.6.3 | 1 CVE record | none |
| 1.6.1 | 2 CVE records | none |
Go 1.6 in dates
| What | When |
|---|---|
| Released | 17 February 2016 |
| Security fixes end | 16 February 2017 |
| Newest release | 1.6.4 (1 December 2016) |
What this page says
Since 16 February 2017, the Go vulnerability database has published advisories that name 230 CVE ids. 8 of them are not placed on a branch. Of the others, 5 give a range of its own for Go 1.6, and 198 give a range with no start that ends in a newer branch; as the advisory states it, that range covers Go 1.6 too.
A record names the branches the project tested, and a branch that has ended is rarely among them. That does not make Go 1.6 safe. Not tested by the project, treat as affected.
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
- 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)
- Package advisories from the Go vulnerability database (CC BY 4.0). Version ranges are reworded as sentences (source). Licence: CC BY 4.0