Quick answers
- Is CVE-2026-16498 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-16498 being exploited in the wild.
- How severe is CVE-2026-16498?
- Critical severity, with a CVSS score of 10, 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-16498?
- A patch was published on 2026-07-28. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-16498 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-16498?
- Check whether you run HashiCorp Terraform-Mcp-Server. 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 vulnerability exists in terraform-mcp-server when configured in stateless HTTP transport mode. The server's per-session Terraform client cache relies on session identifiers to isolate user credentials; however, in stateless mode, the underlying MCP library does not assign unique session identifiers. Consequently, the server fails to correctly isolate credentials across requests, causing the Terraform token supplied by one tenant to be reused for subsequent requests from other tenants. An unauthenticated remote attacker can exploit this to execute tool calls using the permissions of a previous user's token. This issue 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
- 2026-07-28: patched