Go 1.3 End of Life
Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.
Go 1.3 reached end of life on 19 Aug 2015. It no longer receives security fixes.
Support timeline
Official dates, read directly from go.dev.
| Milestone | Date | Status |
|---|---|---|
| Initial release | 18 Jun 2014 | 12y 4mo ago |
| Supported ended | 19 Aug 2015 | 11y 2mo ago |
| Latest release | 1.3.3 · 30 Sept 2014 | final |
The cost of staying: CVEs since end of life
173 Go vulnerabilities have been published since 19 Aug 2015. All were fixed in supported branches — 1.3 received none of them. Source: NVD.
Go CVEs published since 1.3's EOL, by year
22 of the 173 are rated critical · data refreshed 2026-10-05
Published 5 Feb 2026 · rated critical — fixed in supported branches only, never in 1.3. Details
Published 5 Oct 2017 · rated critical — fixed in supported branches only, never in 1.3. Details
Published 18 Oct 2017 · rated critical — fixed in supported branches only, never in 1.3. Details
Where to go from 1.3
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.3 still safe to use?
No. Go 1.3 stopped receiving security fixes on 19 Aug 2015. Since then, 173 Go vulnerabilities have been published and fixed in supported branches — Go 1.3 received none of those fixes.
Can I still download Go 1.3?
Yes — the final release (1.3.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.3 to?
Upgrade to Go 1.27, the newest actively supported branch.