CVE-2026-16326
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.
Scoring
- Severity
- CRITICAL
- CVSS base score
- 10
- CVSS vector
- CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:L
- EPSS probability
- 0.30%
- CWE
- CWE-488
- Published
- 2026-07-29
- Last modified
- 2026-07-29
Affected products
- HashiCorp Tooling
Weakness type
Related vulnerabilities
- CVE-2026-84685 — Improper Cache Isolation in auth0/react-native-auth0 SDK Web Platform Credential Management
- CVE-2026-86492 — In JetBrains YouTrack before 2026.2.18634 a shared token cache allowed cross-tenant theft of GitHub...
- CVE-2026-18489 — IBM ContextForge Translate is affected by cross-client credential context confusion
- CVE-2026-82367 — Re-entrant synchronous publish in AshGraphql subscription batcher delivers one subscriber's records to another's topic
- CVE-2026-71850 — Hono: `memo()` retains SSR output across requests, leading to cross-user data disclosure
- CVE-2026-16498 — terraform-mcp-server vulnerable to cross-tenant credential reuse in streamable-HTTP stateless mode
- CVE-2026-54497 — view_component: Reused Component Instances Retain Stale Render Context
- CVE-2026-14621 — FederatedAI FATE OSX Broker QueuePushReqStreamObserver.java QueuePushReqStreamObserver.initEggroll wrong session