Skip to content
Cloud

CVE-2026-14869

8.6
High
EPSS 0.38%Patch availableJul 29, 2026

Unauthenticated SSRF in terraform-mcp-server redirects API requests and auth tokens

common questions

Is CVE-2026-14869 being exploited?

Not confirmed. CVE-2026-14869 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.38% probability of exploitation in the next 30 days.

How severe is CVE-2026-14869?

CVE-2026-14869 is rated High with a CVSS score of 8.6. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.

Is there a patch for CVE-2026-14869?

Yes. A fix has been recorded for CVE-2026-14869. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.

What does CVE-2026-14869 affect?

CVE-2026-14869 affects terraform-mcp-server < 1.1.0, streamable-HTTP transport component, Terraform API endpoints proxied by the server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.

What should I do about CVE-2026-14869?

Upgrade to terraform-mcp-server 1.1.0; block outbound to untrusted endpoints; rotate exposed tokens.

Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.

executive summary
technical analysis
affected
terraform-mcp-server < 1.1.0streamable-HTTP transport componentTerraform API endpoints proxied by the server
impact

Unauthenticated SSRF allows attacker to redirect Terraform API calls and exfiltrate the server's auth token, enabling request forgery, data theft, and unauthorized actions.

action required

Immediate action required

affected versions
HashiCorp Tooling
  • affected>= 0.3.0 and < 1.1.0

As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.

how to fix
Remediation steps are tailored for users whose stack is affected. Add this technology to your stack to see the fix checklist.
references
get alerted

Track only the vulnerabilities that affect your infrastructure.

start for free