Go 1.0 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Go 1.0 reached end of life on 1 Dec 2013. It no longer receives security fixes.
Support timeline
Official dates, read directly from go.dev.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 28 Mar 2012 | 14y 6mo ago |
| Supported ended | 1 Dec 2013 | 12y 10mo ago |
| Latest release | 1.0.3 · 21 Sept 2012 | final |
The cost of staying: CVEs since end of life
174 Go vulnerabilities have been published since 1 Dec 2013. All were fixed in supported branches — 1.0 received none of them. Source: NVD.
Go CVEs published since 1.0's EOL, by year
22 of the 174 are rated critical · data refreshed 2026-10-05
Published 5 Feb 2026 · rated critical — fixed in supported branches only, never in 1.0. Details
Published 5 Oct 2017 · rated critical — fixed in supported branches only, never in 1.0. Details
Published 18 Oct 2017 · rated critical — fixed in supported branches only, never in 1.0. Details
Where to go from 1.0
Recommended target: Go 1.27.
The newest actively supported branch is Go 1.27 (latest release 1.27.1). Review go.dev before upgrading.
Frequently asked questions
Is Go 1.0 still safe to use?
No. Go 1.0 stopped receiving security fixes on 1 Dec 2013. Since then, 174 Go vulnerabilities have been published and fixed in supported branches — Go 1.0 received none of those fixes.
Can I still download Go 1.0?
Yes — the final release (1.0.3) 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.0 to?
Upgrade to Go 1.27, the newest actively supported branch.