Synced 17 Jun 2026 22:27 UTC Account
← Terraform

Terraform vulnerabilities: known CVEs & security history

HashiCorp · Infrastructure as code · 5 tracked CVEs · 0 actively exploited · updated June 2026 · what is a CVE? →

This is the full list of known vulnerabilities (CVEs) across all Terraform release lines — 5 in total. A CVE here doesn't mean your version is affected — check Terraform's current status and the safe version to run.

5
known CVEs
0
actively exploited (KEV)
1
critical severity
0
ransomware-linked

Known Terraform CVEs

Actively-exploited and most-severe first. Open any CVE for full details.

CVESeverityCVSSEPSSYear
CVE-2018-9057 critical 9.8 2% 2018
CVE-2021-36230 high 8.8 1% 2021
CVE-2019-19316 high 7.5 1% 2019
CVE-2023-4782 medium 6.3 0% 2023
CVE-2025-13432 medium 4.3 0% 2025

Is my Terraform version affected?

The list above spans every release. To know whether your version is affected — and the minimum safe version to upgrade to — check it directly.

Check your Terraform version → · Monitor Terraform for new CVEs →

Terraform vulnerabilities — frequently asked

How many known vulnerabilities does Terraform have?

IsItPatched tracks 5 CVEs for Terraform. 1 is critical-severity and 2 high-severity. These span every release line — what matters is whether the version you run is affected.

Does Terraform have any actively-exploited vulnerabilities?

None of Terraform's tracked CVEs are currently in CISA's KEV catalog — but new ones can be added at any time, so keep your version current.

What is the most severe Terraform vulnerability?

Among tracked issues, CVE-2018-9057 (CRITICAL, CVSS 9.8) ranks highest — a CWE-332 weakness.

Is Terraform safe to use?

It depends on the version. The latest supported Terraform release clears the known issues; older versions may still be affected. Check the exact version you run for a verdict.

CVE data aggregated from NVD, CISA KEV and EPSS (FIRST.org). Related: Terraform security status · Terraform end-of-life · actively-exploited CVEs. Always verify against HashiCorp's advisories — see our disclaimer.