end-of-life.org

Go 1.10 End of Life

Support dates, vulnerabilities published since end of life, and upgrade guidance — rebuilt from live data.

End of Life

Go 1.10 reached end of life on 25 Feb 2019. It no longer receives security fixes.

2,722 days without security patches
156 Go CVEs published since EOL
Recommended action: upgrade to Go 1.26.
Check your versiongo version

Support timeline

Official dates from the Go release process.

MilestoneDateStatus
Initial release16 Feb 2018
End of life 25 Feb 2019 7.5 years ago
Latest release1.10.8 · 23 Jan 2019 final

The cost of staying: CVEs since end of life

156 Go vulnerabilities have been published since 25 Feb 2019. All were fixed in supported branches — 1.10 received none of them. Source: NVD.

Go CVEs published since 1.10's EOL, by year

19 of the 156 are rated critical · data refreshed 2026-08-09

0 20 40 6 2019 13 2020 19 2021 33 2022 32 2023 2 2024 13 2025 38 2026
CVE-2025-68121 CVSS 10

Published 5 Feb 2026 · rated critical — fixed in supported branches only, never in 1.10. Details

CVE-2019-11888 CVSS 9.8

Published 13 May 2019 · rated critical — fixed in supported branches only, never in 1.10. Details

CVE-2019-14809 CVSS 9.8

Published 13 Aug 2019 · rated critical — fixed in supported branches only, never in 1.10. Details

Where to go from 1.10

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.10 still safe to use?

No. Go 1.10 stopped receiving security fixes on 25 Feb 2019. Since then, 156 Go vulnerabilities have been published and fixed in supported branches — Go 1.10 received none of those fixes.

Can I still download Go 1.10?

Yes — the final release (1.10.8) 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.10 to?

Upgrade to Go 1.26, the newest actively supported branch.

All Go versions