NIST deprecates RSA-2048 from 2030. Find every one of them before attackers do.
🐹
🐹 Go
Not in CISA KEV
HIGH severity

Use of a Broken or Risky Cryptographic Algorithm in TerraformGHSA-h3p9-wrgx-82cm

HIGHFix: hashicorp/terraform@6db3cf8

GHSA-h3p9-wrgx-82cm is a high-severity (CVSS 7.5) CWE-319 vulnerability in github.com/hashicorp/terraform. A fix is available for github.com/hashicorp/terraform — see the affected versions and patch details below.

Also known asCVE-2019-19316GHSA-4rvg-555h-r626GO-2022-0839
Published
Updated
Affected
1 pkg
Patched
1 / 1
Exploits
None indexed
Exploitation data as of Nov 11, 2026 · OSV.dev, NVD, FIRST.org (EPSS)

EPSS Exploitation Probability

via FIRST.org ↗
0.9%probability of exploitation in next 30 days
Lower Risk0.00%
Lower risk than most CVEs59th percentile — riskier than 59% of all scored CVEsHighest risk
0.00%0.50%1.00%1.50%0.2%0.9%May 26Sep 26Nov 26

Probability of exploitation in the next 30 days, from FIRST.org EPSS.

How urgent is this, really

Where this sits among everything scored

Real-World Exposure

1 pkg affected
🐹github.com/hashicorp/terraform

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP.

Specific Go Packages Affected

github.com/hashicorp/terraform/backend/remote-state/azure

Affected Packages

1 total 1 fixed
EcosystemPackageVulnerable rangeFix
🐹Gogithub.com/hashicorp/terraformall versions0.12.17go get github.com/hashicorp/terraform@v0.12.17

Affected Products

1 product · 1 configurations
Application
terraformhashicorp
< 0.12.17
range

Detection & mitigation playbook

Open-source dependency

  1. Detect

    Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/hashicorp/terraform, including transitive dependencies — a direct dependency you never call can still pull in a vulnerable version.

  2. Fix

    Update github.com/hashicorp/terraform to 0.12.17 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-h3p9-wrgx-82cm is resolved across your whole dependency graph.

  3. Workarounds

    If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

Frequently Asked Questions

When using the Azure backend with a shared access signature (SAS), Terraform versions prior to 0.12.17 may transmit the token and state snapshot using cleartext HTTP. ### Specific Go Packages Affected github.com/hashicorp/terraform/backend/remote-state/azure
O3 Security · Impact-Aware SCA

Is GHSA-h3p9-wrgx-82cm in your dependencies?

Find it across Go, including transitive dependencies.

Scan my dependencies How O3 SCA works
Use of a Broken or Risky Cryptographic Algorithm in…