CVE-2026-16496
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedThe terraform-mcp-server before version 1.1.0 is vulnerable to an authorization bypass in the streamable-HTTP stateful transport mode that may allow a user who obtains another user's MCP session ID to have their tool calls executed using that user's Terraform credentials. This vulnerability, CVE-2026-16496, is fixed in terraform-mcp-server 1.1.0.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · high confidenceThe terraform-mcp-server before version 1.1.0 has an authorization bypass in its streamable-HTTP stateful transport mode. An attacker who obtains another user's MCP session ID can execute tool calls using the victim's Terraform credentials, effectively hijacking the session and performing actions with the victim's cloud infrastructure access.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- High
- Privileges
- None
- User interaction
- None
- Scope
- Changed
- Confidentiality
- High
- Integrity
- High
- Availability
- Low
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:C/C:H/I:H/A:L
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Identify installed terraform-mcp-server versionRun `terraform-mcp-server --version` or check the binary/package version installed in your environmentAffected if Version is earlier than v1.1.0
-
Locate server configuration fileFind the configuration file (commonly config.json, config.yaml, or environment-based config) used by terraform-mcp-server - check common paths like /etc/terraform-mcp/, ~/.config/terraform-mcp/, or the working directory where the server is launchedAffected if A configuration file exists and the server version is below v1.1.0
-
Verify transport mode configurationInspect the configuration file for the transport setting - look for entries such as `transport`, `http_transport`, or `streamable_http` that specify the transport protocolAffected if Transport mode is set to `streamable-http` or `streamable_http` (stateful mode) AND version is below v1.1.0
-
Check session ID handlingReview server logs or configuration for session token settings - look for `session`, `session_token`, or `auth` related configuration keys that control how MCP session IDs are generated or validatedAffected if Session-based authentication is in use with streamable-HTTP transport and version is below v1.1.0
You are affected if terraform-mcp-server version is earlier than v1.1.0 AND the streamable-HTTP stateful transport mode is enabled, as this combination allows session hijacking via exposed MCP session IDs.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scopedUpgrade terraform-mcp-server to version 1.1.0 or later to remediate this session hijacking vulnerability.
terraform-mcp-server 1.1.0
- Check the currently installed version of terraform-mcp-server
- Upgrade terraform-mcp-server to version 1.1.0 or later
- Verify the upgrade was successful by checking the installed version
Generated from the published advisory — verify against the referenced sources before acting.
- Consultation2.0 h
- Implementation1.0 h
- Testing2.0 h
- Review / QA1.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $1,696.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-16496 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-16496 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data