{"id":"CVE-2026-16328","aliases":["BIT-consul-2026-16328","EUVD-2026-50466","GHSA-5h6c-295f-7pp3"],"status":"published","title":"consul-mcp-server vulnerable to server side request forgery leading to token exposure","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.","severity":{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"cna","from":"cve"},"epss":{"day":"2026-11-11","score":0.00394,"percentile":0.34007,"model":"v2026.06.15"},"facts":{"in_kev":false,"known_exploited":false,"public_exploit":false,"fix_available":true},"cwes":["CWE-918"],"published":"2026-07-29T18:32:39Z","modified":"2026-10-28T02:31:06Z","fixes":[{"ecosystem":"Bitnami","package":"consul","fixed_in":["0.1.4"],"sources":["osv"]}],"affected":[{"source":"osv","ecosystem":"Bitnami","package":"consul","ranges":[{"type":"SEMVER","events":[{"introduced":"0.1.0"},{"fixed":"0.1.4"}]}]}],"products":[{"vendor":"hashicorp","product":"tooling"}],"references":[{"url":"https://discuss.hashicorp.com/t/hcsec-2026-24-multiple-vulnerabilities-impacting-hashicorp-consul-mcp-server/77612","tags":["web"]},{"url":"https://nvd.nist.gov/vuln/detail/CVE-2026-16328","tags":["web","advisory"]},{"url":"https://github.com/advisories/GHSA-5h6c-295f-7pp3"},{"url":"https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/16xxx/CVE-2026-16328.json","tags":["advisory"]},{"url":"https://github.com/hashicorp/consul-mcp-server","tags":["package"]}],"sources":{"cve":[{"id":"CVE-2026-16328","title":"consul-mcp-server vulnerable to server side request forgery leading to token exposure","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.","status":"published","published":"2026-07-29T18:32:39.87Z","modified":"2026-07-29T19:11:05.959Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"cna"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:20:10.870108Z"}],"euvd":[{"id":"EUVD-2026-50466","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.","status":"published","published":"2026-07-29T18:32:39Z","modified":"2026-07-29T19:11:05Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"updated_at":"2026-11-02T18:02:29.807737Z"}],"ghsa":[{"id":"GHSA-5h6c-295f-7pp3","title":"In consul-mcp-server, versions 0.1.0 up to 0.1.3 did not restrict how the Consul backend address...","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.","status":"published","published":"2026-07-29T21:30:59Z","modified":"2026-07-29T21:31:07Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T15:09:54.918351Z"}],"nvd":[{"id":"CVE-2026-16328","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.","status":"published","published":"2026-07-29T19:16:45.06Z","modified":"2026-10-24T13:10:00.147Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high","assessor":"secondary"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T14:12:33.629616Z"}],"osv":[{"id":"CVE-2026-16328","title":"consul-mcp-server vulnerable to server side request forgery leading to token exposure","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.","status":"published","published":"2026-07-29T18:32:39.87Z","modified":"2026-10-28T02:31:06.856435493Z","cvss":[{"version":"3.1","score":8.6,"vector":"CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N","level":"high"}],"cwes":["CWE-918"],"updated_at":"2026-11-02T15:44:57.682091Z"},{"id":"BIT-consul-2026-16328","title":"consul-mcp-server vulnerable to server side request forgery leading to token exposure","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.","status":"published","published":"2026-08-17T05:38:06.696Z","modified":"2026-08-17T08:00:08.609921638Z","updated_at":"2026-11-02T15:28:28.70813Z"}]}}