CVE-2026-16328

HighCVSS 8.6

Published: 29/07/2026(UTC)Updated: 30/07/2026(UTC)Translated: 30/07/2026(UTC)NVD NIST

Exploitation Probability (EPSS)

Low risk

0.23%

14th percentile - higher than 14% of all known CVEs

Summary

In consul-mcp-server versions 0.1.0 through 0.1.3, the Consul backend address was not restricted, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect Consul API traffic to an attacker-controlled endpoint and potentially exfiltrate the Consul token.

Risk Assessment

An attacker can capture the Consul token and gain unauthorized access to the infrastructure managed by Consul, potentially leading to full system compromise.

Recommendation

Upgrade consul-mcp-server to version 0.1.4 or later.

Other vulnerabilities in consul-mcp-server

CVE-2026-16326Critical
A vulnerability in consul-mcp-server versions 0.1.0 through 0.1.3 causes a Consul authentication token from one client to be reused for subsequent requests from other clients in stateless mode. Lack of session state isolation allows unauthorized access to Consul resources.

Original NVD description (English source)

In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address was supplied, allowing a connected client to override the server's configured Consul address via a request header. This may allow a malicious client to redirect the server's Consul API traffic to an attacker-controlled endpoint, potentially exfiltrating the Consul token configured on the server. This vulnerability, CVE-2026-16328, is fixed in consul-mcp-server 0.1.4.