Hashicorp Terraform End of Life (EOL) Dates and End of Support (EOS) Dates

Latest Release: 1.17.2

Hashicorp Terraform end of life (EOL) and end of support (EOS) dates: 16 Hashicorp Terraform versions have reached EOL, including Hashicorp Terraform 1.15 (EOL date: Oct 21, 2026) — no longer receiving security updates or patches. Hashicorp Terraform 1.17.2 is the current supported release — 2 versions in active support. Also see Hashicorp Boundary end of life for related end-of-life information.

Hashicorp Terraform end of life dates timeline — release schedule chart of the 8 most recent Hashicorp Terraform versions, mapping security support windows against their EOL dates
Hashicorp Terraform end of life dates and end of support (EOS) dates shown as a release schedule — support windows for the 8 most recent Hashicorp Terraform releases of 18 total. Each bar runs from the release date to the end of security support, with the dashed line marking today. Exact Hashicorp Terraform EOL, EOS and EOSL dates for every version are listed in the tables below.

Currently Supported Hashicorp Terraform Releases - Active EOS/EOSL Support (2)

Release Released Security Support Latest
1.17 (1 month ago) Active 1.17.2 (1 week and 3 days ago)
1.16 (2 months ago) Active 1.16.7 (4 weeks and 2 days ago)

Hashicorp Terraform End of Life (EOL) Releases - No Longer Supported (16)

Release Released Security Support Latest
1.15 (6 months ago) (1 month ago) 1.15.9 (3 months ago)
1.14 (1 year ago) (2 months ago) 1.14.9 (7 months ago)
1.13 (1 year and 3 months ago) (6 months ago) 1.13.5 (1 year ago)
1.12 (1 year and 6 months ago) (1 year ago) 1.12.2 (1 year and 5 months ago)
1.11 (1 year and 8 months ago) (1 year and 3 months ago) 1.11.4 (1 year and 7 months ago)
1.10 (1 year and 11 months ago) (1 year and 6 months ago) 1.10.5 (1 year and 9 months ago)
1.9 (2 years and 4 months ago) (1 year and 8 months ago) 1.9.8 (2 years and 1 month ago)
1.8 (2 years and 7 months ago) (1 year and 11 months ago) 1.8.5 (2 years and 5 months ago)
1.7 (2 years and 10 months ago) (2 years and 4 months ago) 1.7.5 (2 years and 8 months ago)
1.6 (3 years and 1 month ago) (2 years and 7 months ago) 1.6.6 (2 years and 11 months ago)
1.5 (3 years and 5 months ago) (2 years and 10 months ago) 1.5.7 (3 years and 2 months ago)
1.4 (3 years and 8 months ago) (3 years and 1 month ago) 1.4.7 (3 years and 2 months ago)
1.3 (4 years and 2 months ago) (3 years and 5 months ago) 1.3.10 (3 years and 2 months ago)
1.2 (4 years and 6 months ago) (3 years and 8 months ago) 1.2.9 (4 years and 2 months ago)
1.1 (4 years and 11 months ago) (4 years and 2 months ago) 1.1.9 (4 years and 7 months ago)
1.0 (5 years and 5 months ago) (4 years and 6 months ago) 1.0.11 (5 years ago)

Hashicorp Terraform end of life decides how long the release running your infrastructure as code keeps receiving fixes, and only the newest few versions qualify. This guide covers the dates, the rule behind them and what to do when your release drops off, so your multi-cloud provisioning and automation workflows never run on unpatched software. As of October 27, 2026, the latest Terraform version is 1.17.0, released October 21.

Hashicorp Terraform End of Life Policy

Hashicorp applies one support policy to all its products: generally available releases of active products are supported for up to two years. Bug fixes, hot-fixes and code-fixes that qualify ship in a new minor release on top of the latest major release branch, for up to two releases back from the current one. This EOL policy is what customers should plan against, and the best practice is to stay current within two releases of the newest.

Generally Available Releases and Minor Release Support

A generally available release is one past its beta and release-candidate stages. Support means the vendor investigates defects in that product line; fixes land in a newer minor release, which Hashicorp identifies by the third digit, rather than being back-ported without limit.

How a Major Release Is Identified

Versioning follows X.Y.Z. A change in the first or second digit makes a new major release, so 1.16 and 1.17 are separate lines, while moving from 1.16.5 to 1.16.7 is only a patch version step inside one line.

Terraform Support Period Dates by Release

The table lists each recent release, when it shipped and when its security coverage ended. Dates use ISO format (YYYY-MM-DD), compiled from endoflife.date and Versio.io.

ReleaseRelease dateLatest version in lineSecurity support
1.172026-10-211.17.0Active
1.162026-08-261.16.7Active
1.152026-04-291.15.9Active
1.142025-11-191.14.9Ended 2026-08-26
1.132025-08-201.13.5Ended 2026-04-29
1.122025-05-141.12.2Ended 2025-11-19
1.112025-02-271.11.4Ended 2025-08-20
1.102024-11-261.10.5Ended 2025-05-14
1.92024-06-261.9.8Ended 2025-02-27

Read the table as a lifecycle: each release lost security coverage the day the release two steps newer shipped, so 1.14 ended on 2026-08-26 when 1.16 arrived. By that pattern 1.15 should have dropped when 1.17 shipped, but endoflife.date had not yet listed 1.17 at its October 23 update, so confirm before relying on it. That is my reading of the trend, not a published Hashicorp date. Every release before 1.0 is long past any support.

Latest Version and Pre-Release Builds

Only the newest patch of a supported line gets fixes, so 1.16.7, which followed on October 22 with a fix for a panic in the test command, is the build to run on 1.16. GitHub also lists pre-release builds such as 1.17.0-rc2; they sit outside the support window, so treat them as previews, not production. Read the changelog for a release before you upgrade; its bug fixes show whether a patch affects you, and Hashicorp publishes the policy for each product line alongside.

Which Terraform Versions Get Security Support

The two trackers disagree. endoflife.date marks only 1.16 and 1.15 as covered, while Versio.io counts eleven supported releases, 1.7 through 1.17. They define support differently, so plan around the stricter date. A version past its end carries real security exposure: Versio.io counts 172 versions affected by CVE out of 480 total, plus 193 unstable versions, and a deprecated release gets no fix when the next flaw appears. Your supported release is the only one Hashicorp will patch, and a stable, current build is the cheapest protection against that product risk.

Is There Long-Term Support for Terraform?

No. Versio.io states that Terraform has no LTS releases; every release follows the same standard period.

Check Your Terraform Release with terraform --version

Run terraform --version in the Terraform CLI and compare the result with the table. If you are more than two lines behind, download a newer build and test your configuration against it.

Terraform Enterprise EOL Policy

Terraform Enterprise follows a two-year advisory support policy. The final Replicated release arrived in March 2025, and Hashicorp supports it until April 1, 2026. The core software has also changed licence: Versio.io still calls it an open source tool, but it ships under the Business Source License, so review those terms.

Terraform Cloud Workspaces

Terraform Cloud lets you choose the version a workspace runs, which means the end date that matters is the one for the version you pinned in the cloud, not the newest. A pinned version past its security support date stays unpatched, so raise it before the date in the table.

Terraform 1.0 Maintenance Period and Terraform Plugin SDK Changes

When Terraform 1.0 reached general availability on June 8, 2021, Hashicorp promised a maintenance period of at least 18 months for every 1.x release and a stable feature set. State became cross-compatible between 0.14.x, 0.15.x and 1.0.x, and remote state compatibility was back-ported to 0.12.30 and 0.13.6, so terraform state stays readable while you move. Support for version 1 of the Terraform Plugin SDK also ended on July 31, 2021, which concerned only developers of each provider, since Terraform 1.0 users of the CLI were unaffected and providers were what changed; the documentation and community forum cover that move. Declarative configuration written for the CLI needed no change. Each provider keeps its own version constraints, so a provider release can set a stricter floor than the CLI, and the provider changelog is worth reading before an upgrade. Hashicorp set this policy to make upgrades predictable.

Upgrade Path from 0.14 to 1.x

Releases at 0.14 and earlier are long past support, which is why moving to 1.x matters. Since 0.15, workflows keep working across upgrades without refactoring or special tools. Read the upgrade guide only for jumps from older lines, apply each patch, then run a plan before you apply.