Go End of Life Dates
language
Developers seeking a high-level, general-purpose programming language that is statically typed and compiled often turn to Go, which was created to provide simplicity of syntax and efficiency of development. With a large standard library, Go enables rapid development and has been maintained by its community since its inception. The language's efficiency and simplicity have made it a popular choice among developers, who appreciate the ease of use and the speed at which they can create applications. Go's maintainers continue to update and refine the language, ensuring it remains a viable option for building a wide range of applications.
The end-of-life landscape for Go is characterized by a total of 17 versions, with 15 of these versions having reached their end-of-life. Currently, only 2 versions remain active, with the latest stable version being 1.25.11. The most recent version to reach its end-of-life was 1.24, which occurred on 2026-02-11. Notably, there is no next scheduled end-of-life date, providing developers with a stable and secure environment for their applications. This landscape underscores the importance of staying up-to-date with the latest versions of Go to ensure continued support and security.
The security picture for Go is marked by a total of 522 tracked CVEs, with 34 of these being critical. Version 1.24 is the most affected, with 31 CVEs, highlighting the potential risks associated with using outdated versions. Developers should take action to ensure they are using a supported version of Go, such as the latest stable version 1.25.11, to mitigate these risks and protect their applications from potential vulnerabilities. By staying informed about the security landscape and taking proactive steps, developers can minimize their exposure to security threats and maintain the integrity of their applications.
Last updated: Sep 7, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.27 | Aug 19, 2026 | — | No | — | 1.27.1 | — | Active | |
| 1.26 | Feb 10, 2026 | — | No | — | 1.26.8 | Active | ||
| 1.25 | Aug 12, 2025 | — | Aug 19, 2026 | 19d ago | 1.25.14 | EOL | ||
| 1.24 | Feb 11, 2025 | — | Feb 10, 2026 | 209d ago | 1.24.13 | EOL | ||
| 1.23 | Aug 13, 2024 | — | Aug 12, 2025 | 391d ago | 1.23.12 | EOL | ||
| 1.22 | Feb 6, 2024 | — | Feb 11, 2025 | 573d ago | 1.22.12 | EOL | ||
| 1.21 | Aug 8, 2023 | — | Aug 13, 2024 | 755d ago | 1.21.13 | EOL | ||
| 1.20 | Feb 1, 2023 | — | Feb 6, 2024 | 944d ago | 1.20.14 | EOL | ||
| 1.19 | Aug 2, 2022 | — | Sep 6, 2023 | 1097d ago | 1.19.13 | EOL | ||
| 1.18 | Mar 15, 2022 | — | Feb 1, 2023 | 1314d ago | 1.18.10 | EOL | ||
| 1.17 | Aug 16, 2021 | — | Aug 2, 2022 | 1497d ago | 1.17.13 | EOL | ||
| 1.16 | Feb 16, 2021 | — | Mar 15, 2022 | 1637d ago | 1.16.15 | EOL | ||
| 1.15 | Aug 11, 2020 | — | Aug 16, 2021 | 1848d ago | 1.15.15 | EOL | ||
| 1.14 | Feb 25, 2020 | — | Feb 16, 2021 | 2029d ago | 1.14.15 | EOL | ||
| 1.13 | Sep 3, 2019 | — | Aug 11, 2020 | 2218d ago | 1.13.15 | EOL | ||
| 1.12 | Feb 25, 2019 | — | Feb 25, 2020 | 2386d ago | 1.12.17 | EOL | ||
| 1.11 | Aug 24, 2018 | — | Sep 3, 2019 | 2561d ago | 1.11.13 | EOL | ||
| 1.10 | Feb 16, 2018 | — | Feb 25, 2019 | 2751d ago | 1.10.8 | EOL |
Data sourced from endoflife.date · CVE data from NVD
