The 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.
CVE-2026-16496
Score 8.9 from GitHub Security Advisory (severity: HIGH) published 2026-07-28. a secondary CVSS source baseline 8.9; sources differ by 0.0.
- High severity, but no confirmed exploitation yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 8.9
- EG Score
- 8.9(high)
- EG Risk
- 40(Track)EG Risk 40/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity89% × 45%Exploitation0% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS PROB
- —
- EPSS %ILE
- —
- KEV
- Not listed
Published
July 28, 2026
Last Modified
July 28, 2026
Advisory Details (1)
Auto-updated Jul 28, 2026HCSEC-2026-23 - Multiple vulnerabilities impacting HashiCorp Terraform MCP Server - Security - HashiCorp Discuss
https://discuss.hashicorp.com/t/hcsec-2026-23-multiple-vulnerabilities-impacting-hashicorp-terraform-mcp-server/77606Vendor Advisories for CVE-2026-16496(2)
These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 5× in last 7d / 5× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-29 07:54 UTCEG score recompute
- 2026-07-29 07:54 UTCGHSA enrichment
- 2026-07-28 19:27 UTCEG score recompute
- 2026-07-28 19:00 UTCEG score recompute
- 2026-07-28 18:22 UTCEG score recompute
Related CVEs(same CWE)
Same CWE
10 shownCWE-384
- CVE-2018-18926EG 9.8CRITICAL
- CVE-2018-18925EG 9.8EPSS p98CRITICAL
- CVE-2016-6545EG 9.8CRITICAL
- CVE-2018-12071EG 9.8CRITICAL
- CVE-2018-11714EG 9.8EPSS p98CRITICAL
- CVE-2017-15304EG 9.8CRITICAL
- CVE-2016-10405EG 9.8CRITICAL
- CVE-2017-12873EG 9.8CRITICAL
- CVE-2017-12868EG 9.8CRITICAL
- CVE-2017-12965EG 9.8EPSS p97CRITICAL
Frequently asked(4)
What is CVE-2026-16496?
When was CVE-2026-16496 disclosed?
What is the CVSS score of CVE-2026-16496?
How do I remediate CVE-2026-16496?
Dependency Blast Radius
Explore the affected products and dependency analysis for CVE-2026-16496
Is Your Infrastructure Affected by CVE-2026-16496?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.