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 | 2630 days past EOL | EOL |
| 1.11 | 1.11.13 | Aug 24, 2018 | Sep 3, 2019 | 2440 days past EOL | EOL |
| 1.12 | 1.12.17 | Feb 25, 2019 | Feb 25, 2020 | 2265 days past EOL | EOL |
| 1.13 | 1.13.15 | Sep 3, 2019 | Aug 11, 2020 | 2097 days past EOL | EOL |
| 1.14 | 1.14.15 | Feb 25, 2020 | Feb 16, 2021 | 1908 days past EOL | EOL |
| 1.15 | 1.15.15 | Aug 11, 2020 | Aug 16, 2021 | 1727 days past EOL | EOL |
| 1.16 | 1.16.15 | Feb 16, 2021 | Mar 15, 2022 | 1516 days past EOL | EOL |
| 1.17 | 1.17.13 | Aug 16, 2021 | Aug 2, 2022 | 1376 days past EOL | EOL |
| 1.18 | 1.18.10 | Mar 15, 2022 | Feb 1, 2023 | 1193 days past EOL | EOL |
| 1.19 | 1.19.13 | Aug 2, 2022 | Sep 6, 2023 | 976 days past EOL | EOL |
| 1.20 | 1.20.14 | Feb 1, 2023 | Feb 6, 2024 | 823 days past EOL | EOL |
| 1.21 | 1.21.13 | Aug 8, 2023 | Aug 13, 2024 | 634 days past EOL | EOL |
| 1.22 | 1.22.12 | Feb 6, 2024 | Feb 11, 2025 | 452 days past EOL | EOL |
| 1.23 | 1.23.12 | Aug 13, 2024 | Aug 12, 2025 | 270 days past EOL | EOL |
| 1.24 | 1.24.13 | Feb 11, 2025 | Feb 11, 2026 | 87 days past EOL | EOL |
| 1.25 | 1.25.10 | Aug 12, 2025 | Already EOL | Supported | Active |
| 1.26 | 1.26.3 | Feb 11, 2026 | Already EOL | Supported | Active |
When a Go version 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.
Upload requirements.txt, package.json, or Gemfile — full EOL report instantly.
Open Stack Scanner →