Quick answers
- Is CVE-2026-14869 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-14869 being exploited in the wild.
- How severe is CVE-2026-14869?
- High severity, with a CVSS score of 8.6, published 28 July 2026.
- Which products and versions are affected?
- HashiCorp Terraform-Mcp-Server 0.2.1 up to and including 1.0.0.
- Is there a fix for CVE-2026-14869?
- A patch was published on 2026-07-28: Fixed in version 1.1.0 Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-14869 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-14869?
- Check whether you run HashiCorp Terraform-Mcp-Server at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A Server-Side Request Forgery (SSRF) vulnerability exists in the streamable-HTTP transport of terraform-mcp-server. The vulnerability is caused by insufficient validation of client-supplied Terraform addresses when provided as an HTTP query parameter, even though the server correctly rejected such addresses when provided in HTTP headers. An unauthenticated remote attacker can supply a malicious URL via a query parameter, causing the server to send its configured bearer token to the attacker-controlled endpoint. This issue affects deployments using the streamable-HTTP listener; deployments using stdio mode exclusively are not impacted. The vulnerability is fixed in version 1.1.0.
Affected products
- HashiCorp terraform-mcp-server 0.2.1 up to and including 1.0.0
Timeline
- 2026-07-28: disclosed: Initial advisory published by HashiCorp
- 2026-07-28: patched: Fixed in version 1.1.0