CVE-2026-14869 HashiCorp CVE debrief

Who should care

Defenders responsible for terraform-mcp-server deployments, especially those handling sensitive Terraform configurations or API requests, should assess exposure and take immediate action to update vulnerable instances or apply compensating controls.

Why it matters

CVE-2026-14869 is a server-side request forgery vulnerability in terraform-mcp-server that allows unauthenticated clients to redirect Terraform API requests. Defenders should prioritize verifying exposure, updating vulnerable instances, and monitoring for suspicious activity.

• Potential unauthorized access to sensitive Terraform configurations or API requests.
• Possible redirection of server-side authorization tokens to attacker-controlled endpoints.
• Need for verification of terraform-mcp-server instances for exposure.
• Priority for updating vulnerable instances to version 1.1.0 or applying compensating controls.

Technical summary

The terraform-mcp-server before version 1.1.0 is vulnerable to a server-side request forgery (SSRF) issue in the streamable-HTTP transport. This allows an unauthenticated remote client to redirect the server's Terraform API requests, and the server-side authorization token, to an attacker-controlled endpoint. The vulnerability is fixed in terraform-mcp-server version 1.1.0. The vulnerability has a high CVSS score of 8.6, indicating a significant risk. Defenders should prioritize verifying exposure of terraform-mcp-server instances, especially those handling sensitive Terraform configurations or API requests.

Defensive priority

Defenders should prioritize verifying exposure of terraform-mcp-server instances, especially those handling sensitive Terraform configurations or API requests. Immediate action is required to update vulnerable instances to version 1.1.0 or apply compensating controls to restrict access to the Terraform API.

Recommended defensive actions

• Verify terraform-mcp-server instances for exposure, especially those handling sensitive Terraform configurations or API requests.
• Update vulnerable instances to terraform-mcp-server version 1.1.0 or later.
• Implement compensating controls to restrict access to the Terraform API and monitor for suspicious activity.
• Review relevant monitoring, detection, and logs for exposed assets that need extra review.
• Track exceptions, retest remediated assets, and close the item only after evidence is documented.
• Confirm whether affected product deployments exist in managed environments and assign an owner for follow-up.
• Plan vendor-supported updates or mitigations through normal change control where exposure is confirmed.

Evidence notes

The CVE record and NVD entry provide details on the vulnerability, its impact, and the fixed version. However, additional information on potential exploitation or affected deployments is limited. The terraform-mcp-server before version 1.1.0 is vulnerable to a server-side request forgery issue in the streamable-HTTP transport. Evidence from the CVE Program and NVD suggests that defenders should verify exposure of terraform-mcp-server instances, especially those handling sensitive Terraform configurations or API requests. There is no 3

Sources and references

Methodology and review provenance

AI-assisted synthesis based on stored public vulnerability evidence. System validation, approval state, and publication status do not by themselves establish human review of this revision. PatchSiren helps prioritize defensive review and does not prove exposure or remediation on any system.