https://db.gcve.eu/rss/recent/all/10 Most recent entries from all 2026-09-28T14:05:22.379008+00:00 Vulnerability-Lookup info@gcve.eu python-feedgen Contains only the most 10 recent entries. https://db.gcve.eu/vuln/bit-consul-2026-16328 BIT-consul-2026-16328 — consul-mcp-server vulnerable to server side request forgery leading to token exposure 2026-09-28T14:05:22.409029+00:00

Affected: Bitnami: consul

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.

 https://db.gcve.eu/vuln/fkie_cve-2026-16328 fkie_cve-2026-16328 2026-09-28T14:05:22.409110+00:00

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.

 https://db.gcve.eu/vuln/ghsa-5h6c-295f-7pp3 GHSA-5h6c-295f-7pp3 2026-09-28T14:05:22.409157+00:00

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.