Go 1.17 · Version Status
Go 1.17 End of Life Date
Go 1.17 end-of-life date, support status, and CVE risk. Data from endoflife.date and official vendor documentation.
⚠
Go 1.17 is past end of life. This version no longer receives security patches. 1376 days past EOL — migrate to a supported version immediately.
EOL Date
Aug 2, 2022
1376 days past EOL
Latest Release
1.17.13
Standard release
Release Date
Aug 16, 2021
Go 1.17 series
| Version | Latest | EOL Date | Status |
|---|
| 1.10 |
1.10.8 |
Feb 25, 2019 |
EOL |
| 1.11 |
1.11.13 |
Sep 3, 2019 |
EOL |
| 1.12 |
1.12.17 |
Feb 25, 2020 |
EOL |
| 1.13 |
1.13.15 |
Aug 11, 2020 |
EOL |
| 1.14 |
1.14.15 |
Feb 16, 2021 |
EOL |
| 1.15 |
1.15.15 |
Aug 16, 2021 |
EOL |
| 1.16 |
1.16.15 |
Mar 15, 2022 |
EOL |
| → 1.17 |
1.17.13 |
Aug 2, 2022 |
EOL |
What does Go 1.17 end of life mean?
When Go 1.17 reaches end of life, the maintainers stop issuing security patches for this version. CVEs discovered after the EOL date are publicly disclosed on the National Vulnerability Database with no patch available. Exploit code frequently appears on GitHub within days of disclosure.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the ongoing accumulation of unpatched vulnerabilities in EOL software versions. Running Go 1.17 past its EOL date creates a permanently growing attack surface that standard security tooling will not surface.
Migrate to Go 1.26 or implement compensating controls — network segmentation, enhanced monitoring, restricted access — while migration is underway.
Frequently Asked Questions
When does Go 1.17 reach end of life?
Go 1.17 reached end of life on August 2, 2022. This version is no longer receiving security patches.
Is Go 1.17 still supported?
No. Go 1.17 reached end of life on August 2, 2022 and is no longer receiving security patches.
What should I upgrade to from Go 1.17?
The recommended upgrade from Go 1.17 is
Go 1.26 — the latest actively supported version. Check the
Go full timeline for all supported versions.
What are the security risks of running Go 1.17 past EOL?
When Go 1.17 reaches end of life, the maintainers stop issuing security patches. Any CVEs disclosed after the EOL date accumulate with no remediation path. Most vulnerability scanners do not flag this — it is the CVE blind spot. Organizations running EOL Go should migrate immediately or implement compensating controls.