Go 1.17 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Go 1.17 reached end of life on 2 Aug 2022. It no longer receives security fixes.
Support timeline
Official dates from the Go release process.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 16 Aug 2021 | — |
| End of life | 2 Aug 2022 | 4.0 years ago |
| Latest release | 1.17.13 · 1 Aug 2022 | final |
The cost of staying: CVEs since end of life
106 Go vulnerabilities have been published since 2 Aug 2022. All were fixed in supported branches — 1.17 received none of them. Source: NVD.
Go CVEs published since 1.17's EOL, by year
10 of the 106 are rated critical · data refreshed 2026-08-09
Published 5 Feb 2026 · rated critical — fixed in supported branches only, never in 1.17. Details
Published 6 Apr 2023 · rated critical — fixed in supported branches only, never in 1.17. Details
Published 11 May 2023 · rated critical — fixed in supported branches only, never in 1.17. Details
Where to go from 1.17
Recommended target: Go 1.26.
The newest actively supported branch is Go 1.26 (latest release 1.26.5). Review go.dev before upgrading.
Frequently asked questions
Is Go 1.17 still safe to use?
No. Go 1.17 stopped receiving security fixes on 2 Aug 2022. Since then, 106 Go vulnerabilities have been published and fixed in supported branches — Go 1.17 received none of those fixes.
Can I still download Go 1.17?
Yes — the final release (1.17.13) generally remains available from vendor archives and OS package mirrors, but installing it means running software with known, unpatched vulnerabilities.
What should I upgrade Go 1.17 to?
Upgrade to Go 1.26, the newest actively supported branch.