CVE-2026-16498

CRITICALPre-NVD 10.010.0
EchelonGraph scoreHIGH confidence

Score 10.0 from GitHub Security Advisory (severity: CRITICAL) published 2026-07-28. a secondary CVSS source baseline 10.0; sources differ by 0.0.

Triggered by: GitHub Security Advisory CVSS
Sources: ghsa, secondary
10.0EG
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS PROB: CVSS: 10.0Exploit: None knownExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

The terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that may allow one user's Terraform token to be used to execute tool calls on behalf of subsequent users. This vulnerability, CVE-2026-16498, is fixed in terraform-mcp-server 1.1.0.

CVSS v3
10.0
EG Score
10.0(high)
EG Risk
60(Track)
EG Risk 60/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 computed
Severity100% × 45%
Exploitation0% × 40%
Automatability100% × 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, 2026
No patch confirmed yet.
generic

HCSEC-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/77606

Vendor Advisories for CVE-2026-16498(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 7× in last 7d / 7× 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.

  1. 2026-07-29 06:34 UTCGHSA enrichment
  2. 2026-07-29 02:53 UTCGHSA enrichment
  3. 2026-07-28 23:11 UTCEG score recompute
  4. 2026-07-28 23:11 UTCGHSA enrichment
  5. 2026-07-28 19:27 UTCEG score recompute
  6. 2026-07-28 19:00 UTCEG score recompute
  7. 2026-07-28 18:22 UTCEG score recompute

Frequently asked(4)

What is CVE-2026-16498?
CVE-2026-16498 is a critical vulnerability published on July 28, 2026. The terraform-mcp-server before version 1.1.0 is vulnerable to a cross-tenant credential reuse issue in the streamable-HTTP stateless transport mode that may allow one user's Terraform token to be used to execute tool calls on behalf of subsequent users. This vulnerability, CVE-2026-16498, is fixed…
When was CVE-2026-16498 disclosed?
CVE-2026-16498 was first published in the National Vulnerability Database on July 28, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
What is the CVSS score of CVE-2026-16498?
CVE-2026-16498 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-16498?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-16498, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

Explore the affected products and dependency analysis for CVE-2026-16498

Explore →

Is Your Infrastructure Affected by CVE-2026-16498?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.