end-of-life.org

Go 1.20 End of Life

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

End of Life

Go 1.20 reached end of life on 6 Feb 2024. It no longer receives security fixes.

915 days without security patches
53 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 release1 Feb 2023
End of life 6 Feb 2024 2.5 years ago
Latest release1.20.14 · 6 Feb 2024 final

The cost of staying: CVEs since end of life

53 Go vulnerabilities have been published since 6 Feb 2024. All were fixed in supported branches — 1.20 received none of them. Source: NVD.

Go CVEs published since 1.20's EOL, by year

4 of the 53 are rated critical · data refreshed 2026-08-09

0 20 40 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.20. Details

CVE-2024-24790 CVSS 9.8

Published 5 Jun 2024 · rated critical — fixed in supported branches only, never in 1.20. Details

CVE-2026-27143 CVSS 9.8

Published 8 Apr 2026 · rated critical — fixed in supported branches only, never in 1.20. Details

Where to go from 1.20

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

No. Go 1.20 stopped receiving security fixes on 6 Feb 2024. Since then, 53 Go vulnerabilities have been published and fixed in supported branches — Go 1.20 received none of those fixes.

Can I still download Go 1.20?

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

Upgrade to Go 1.26, the newest actively supported branch.

All Go versions