Go versions
Go: update to 1.27.4 or 1.26.11. 1.25 and older no longer get fixes.
Data: .
Which Go branch to run
The newest safe release is the newest release of a branch that still gets fixes and that no CVE record we read names as affected. Records whose versions we cannot place on a branch are named at the end of the page.
| Branch | Status | Newest safe release | Upgrade to |
|---|---|---|---|
| 1.2728 CVE records | Fixes, no end date announced | 1.27.4 | 1.27.4 (this branch) |
| 1.2669 CVE records | Fixes, no end date announced | 1.26.11 | 1.26.11 (this branch) |
| 1.2557 CVE records | Ended on 19 August 2026 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2427 CVE records | Ended on 10 February 2026 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2314 CVE records | Ended on 12 August 2025 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2217 CVE records | Ended on 11 February 2025 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2120 CVE records | Ended on 13 August 2024 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2026 CVE records | Ended on 6 February 2024 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.1926 CVE records | Ended on 6 September 2023 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.1825 CVE records | Ended on 1 February 2023 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.1727 CVE records | Ended on 2 August 2022 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.1619 CVE records | Ended on 15 March 2022 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.1514 CVE records | Ended on 16 August 2021 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.149 CVE records | Ended on 16 February 2021 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.137 CVE records | Ended on 11 August 2020 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.128 CVE records | Ended on 25 February 2020 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.118 CVE records | Ended on 3 September 2019 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.105 CVE records | Ended on 25 February 2019 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.93 CVE records | Ended on 24 August 2018 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.82 CVE records | Ended on 16 February 2018 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.72 CVE records | Ended on 24 August 2017 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.65 CVE records | Ended on 16 February 2017 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.53 CVE records | Ended on 15 August 2016 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.43 CVE records | Ended on 17 February 2016 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.3 | Ended on 19 August 2015 | None, the branch has ended | 1.26.11 (move to 1.26) |
| 1.2 | Ended on 10 December 2014 | None, the branch has ended | 1.26.11 (move to 1.26) |
Exploited, or likely to be
CVE records for Go that CISA lists as exploited, that have a public exploit, or that EPSS rates 0.50 or more, with the release that fixes each in every branch.
| Record | Signs of exploitation | Fixed in |
|---|---|---|
| CVE-2020-0601Certificate validation bypass on Windows in crypto/x509 | On CISA's list Exploit-DB entry EPSS 0.50 or more | Fixed in 1.13.7, 1.12.16 |
| CVE-2023-45288HTTP/2 CONTINUATION flood in net/http | EPSS 0.50 or more | Fixed in 1.22.2, 1.21.9 |
| CVE-2019-9512Reset flood in net/http and golang.org/x/net/http | EPSS 0.50 or more | Fixed in 1.12.8, 1.11.13 |
| CVE-2019-9514Reset flood in net/http and golang.org/x/net/http | EPSS 0.50 or more | Fixed in 1.12.8, 1.11.13 |
| CVE-2018-16873Remote command execution via "go get" with "-u" flag in cmd/go | EPSS 0.50 or more | Fixed in 1.11.3, 1.10.6 |
| CVE-2018-7187Remote command execution via "go get" command with "-insecure" option in cmd/go | EPSS 0.50 or more | Fixed in 1.10.1, 1.9.5 |
What this page counts
The branches, their dates and the newest release of each are from the product lifecycle data credited under Sources. A later release that a CVE record names as a fix counts as the newest too.
The fixes are from 222 CVE ids that advisories of the Go vulnerability database name for Go. An advisory says a release fixes a flaw when its affected range for a branch ends before that release. A record from any other source gives no version here.
A branch that has ended is rarely named in a new record. That is not a sign that it is safe. Not tested by the project, treat as affected.
A release gets a page of its own when it fixes three or more CVE records, or any record that CISA lists as exploited or that EPSS rates 0.50 or more, and keeps it. Any other release is a row on its branch page.
Some records give a range with no start: from 0, or before a release. A record is placed on the branch of the release that ends its range. As the record states it, the range also covers every older release. Such a range is not counted when the newest safe release of a branch that still gets fixes is worked out.
A range that holds only pre-releases (alphas, betas and release candidates) is left out. A record whose fix is a release candidate says so in its row, and the release candidate is not listed as a release.
8 records are not placed on a branch, so no branch or release row counts them: CVE-2014-7189, CVE-2017-8932, CVE-2017-15042, CVE-2023-24531, CVE-2023-45283, CVE-2024-45340, CVE-2025-22865 and CVE-2025-22867.
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