Go End of Life (EOL) Dates & Support Timeline
Complete end-of-life dates, support windows, and security status for all Go versions. Data sourced from endoflife.date and official vendor documentation. Updated at every deploy.
| Version | Latest Release | Release Date | EOL Date | Days | Status |
|---|---|---|---|---|---|
| 1.10 | 1.10.8 | Feb 16, 2018 | Feb 25, 2019 | 2675 days past EOL | EOL |
| 1.11 | 1.11.13 | Aug 24, 2018 | Sep 3, 2019 | 2485 days past EOL | EOL |
| 1.12 | 1.12.17 | Feb 25, 2019 | Feb 25, 2020 | 2310 days past EOL | EOL |
| 1.13 | 1.13.15 | Sep 3, 2019 | Aug 11, 2020 | 2142 days past EOL | EOL |
| 1.14 | 1.14.15 | Feb 25, 2020 | Feb 16, 2021 | 1953 days past EOL | EOL |
| 1.15 | 1.15.15 | Aug 11, 2020 | Aug 16, 2021 | 1772 days past EOL | EOL |
| 1.16 | 1.16.15 | Feb 16, 2021 | Mar 15, 2022 | 1561 days past EOL | EOL |
| 1.17 | 1.17.13 | Aug 16, 2021 | Aug 2, 2022 | 1421 days past EOL | EOL |
| 1.18 | 1.18.10 | Mar 15, 2022 | Feb 1, 2023 | 1238 days past EOL | EOL |
| 1.19 | 1.19.13 | Aug 2, 2022 | Sep 6, 2023 | 1021 days past EOL | EOL |
| 1.20 | 1.20.14 | Feb 1, 2023 | Feb 6, 2024 | 868 days past EOL | EOL |
| 1.21 | 1.21.13 | Aug 8, 2023 | Aug 13, 2024 | 679 days past EOL | EOL |
| 1.22 | 1.22.12 | Feb 6, 2024 | Feb 11, 2025 | 497 days past EOL | EOL |
| 1.23 | 1.23.12 | Aug 13, 2024 | Aug 12, 2025 | 315 days past EOL | EOL |
| 1.24 | 1.24.13 | Feb 11, 2025 | Feb 11, 2026 | 132 days past EOL | EOL |
| 1.25 | 1.25.11 | Aug 12, 2025 | TBD | Supported | Active |
| 1.26 | 1.26.4 | Feb 11, 2026 | TBD | Supported | Active |
What does Go end of life mean for your organization?
When a version of Go reaches end of life, the maintainers stop issuing security patches. Vulnerabilities discovered after this date are publicly disclosed on the National Vulnerability Database, exploit code appears on GitHub, and your systems remain permanently exposed.
The CVE blind spot: Most vulnerability scanners check for known CVEs but do not flag the accumulation of unpatched vulnerabilities in EOL software. With a zero-day, nobody knows about the vulnerability. With EOL software, the vulnerability is public — listed, rated, and often weaponized — but no patch will ever exist. This is the most dangerous gap in enterprise security posture.
Organizations running EOL Go should treat it as a vulnerability class in their risk register, apply compensating controls (network segmentation, enhanced monitoring, access restriction), and prioritize migration to a supported version.
Extended Support Options
If you cannot migrate immediately, extended support vendors provide continued security patches for EOL Go versions. This is a bridge, not a permanent solution — plan your migration in parallel.
We work with vetted extended support vendors. Tell us what you need and we'll connect you with the right provider.
Contact Us →