Terraform End of Life Dates
devops
Developers rely on Terraform to manage and version control their infrastructure, a crucial task in the devops landscape. Created to solve the problem of infrastructure management, Terraform has been a staple in the industry, maintained by HashiCorp, a well-known company in the devops space. Terraform was first introduced to help teams manage their infrastructure in a more efficient and automated way, and since its inception, it has become a widely-used tool among developers. With its ability to track and manage infrastructure, Terraform has become an essential part of many development workflows.
Terraform has a total of 16 versions, with 14 of these versions having reached their end-of-life. The remaining 2 versions are still actively supported, with the latest stable version being 1.14.9. The most recent version to reach its end-of-life was version 1.13, which occurred on 2026-04-29. Fortunately, there is no next end-of-life date announced, giving developers ample time to plan and prepare for any future upgrades. This information is crucial for developers to ensure they are running supported versions of Terraform and can plan their upgrades accordingly.
The security landscape for Terraform is relatively clean, with a total of 0 CVEs tracked and 0 critical CVEs. As a result, there is no most affected version, and no known vulnerabilities pose an immediate risk to users. Additionally, since there are no known vulnerabilities, Terraform is not listed on the Known Exploited Vulnerabilities catalog. Given this information, developers can continue to use Terraform with confidence, but it is still important to keep their versions up to date to ensure they have the latest features and security patches. By staying informed about the latest Terraform versions and security updates, developers can ensure their infrastructure remains secure and well-maintained.
Last updated: Oct 23, 2026
| Version | Released | Active support | EOL date | Until EOL | Latest | CVEs | Status | Alert me |
|---|---|---|---|---|---|---|---|---|
| 1.16 | Aug 26, 2026 | — | No | — | 1.16.7 | — | Active | |
| 1.15 | Apr 29, 2026 | — | No | — | 1.15.9 | — | Active | |
| 1.14 | Nov 19, 2025 | — | Aug 26, 2026 | 58d ago | 1.14.9 | — | EOL | |
| 1.13 | Aug 20, 2025 | — | Apr 29, 2026 | 177d ago | 1.13.5 | — | EOL | |
| 1.12 | May 14, 2025 | — | Nov 19, 2025 | 338d ago | 1.12.2 | — | EOL | |
| 1.11 | Feb 27, 2025 | — | Aug 20, 2025 | 429d ago | 1.11.4 | — | EOL | |
| 1.10 | Nov 26, 2024 | — | May 14, 2025 | 527d ago | 1.10.5 | — | EOL | |
| 1.9 | Jun 26, 2024 | — | Feb 27, 2025 | 603d ago | 1.9.8 | — | EOL | |
| 1.8 | Apr 10, 2024 | — | Nov 26, 2024 | 696d ago | 1.8.5 | — | EOL | |
| 1.7 | Jan 17, 2024 | — | Jun 26, 2024 | 849d ago | 1.7.5 | — | EOL | |
| 1.6 | Oct 4, 2023 | — | Apr 10, 2024 | 926d ago | 1.6.6 | — | EOL | |
| 1.5 | Jun 12, 2023 | — | Jan 17, 2024 | 1010d ago | 1.5.7 | — | EOL | |
| 1.4 | Mar 8, 2023 | — | Oct 4, 2023 | 1115d ago | 1.4.7 | — | EOL | |
| 1.3 | Sep 21, 2022 | — | Jun 12, 2023 | 1229d ago | 1.3.10 | — | EOL | |
| 1.2 | May 18, 2022 | — | Mar 8, 2023 | 1325d ago | 1.2.9 | — | EOL | |
| 1.1 | Dec 8, 2021 | — | Sep 21, 2022 | 1493d ago | 1.1.9 | EOL | ||
| 1.0 | Jun 8, 2021 | — | May 18, 2022 | 1619d ago | 1.0.11 | EOL |
Data sourced from endoflife.date · CVE data from NVD
