CVE-2026-16328 consul-mcp-server vulnerable to server side request forgery leading to token exposure
A malicious client can redirect Consul API traffic to an attacker-controlled endpoint, potentially exposing the server's Consul token.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-16328?
CVE-2026-16328 is a high-severity server-side request forgery vulnerability in HashiCorp Tooling, published on 29 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
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.
Weakness: CWE-918
Which versions are affected by CVE-2026-16328?
1 open source package ship an affected version, including consul.
| Package | Affected | Fixed in |
|---|---|---|
consul Bitnami | From 0.1.0 | 0.1.4 |
How do I fix CVE-2026-16328?
Upgrade consul to 0.1.4 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-16328 being exploited?
There is no known exploitation of CVE-2026-16328 in the wild and no public exploit code.
Sources
Also known as BIT-consul-2026-16328, GHSA-5h6c-295f-7pp3.