CVE-2026-16328

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.

CVSS v3 8.6 HIGH

8.6^/10

CVSS v3 : HIGH

Vector :

Exploitability : 3.9 / Impact : 4.0

Attack Vector NETWORK

Attack Complexity LOW

Privileges Required NONE

User Interaction NONE

Confidentiality Impact HIGH

Integrity Impact NONE

Availability Impact NONE

Scope CHANGED

References

Link	Resource
https://discuss.hashicorp.com/t/hcsec-2026-24-multiple-vulnerabilities-impacting-hashicorp-consul-mcp-server/77612

Configurations

No configuration.

History

24 Oct 2026, 13:10

Type	Values Removed	Values Added
Summary		(es) En consul-mcp-server, las versiones 0.1.0 hasta la 0.1.3 no restringían cómo se suministraba la dirección del backend de Consul, permitiendo a un cliente conectado anular la dirección de Consul configurada del servidor a través de una cabecera de solicitud. Esto puede permitir a un cliente malicioso redirigir el tráfico de la API de Consul del servidor a un endpoint controlado por un atacante, potencialmente exfiltrando el token de Consul configurado en el servidor. Esta vulnerabilidad, CVE-2026-16328, está corregida en consul-mcp-server 0.1.4.

Information

Published : 2026-07-29 19:16

Updated : 2026-10-24 13:10

NVD link : CVE-2026-16328

Mitre link : CVE-2026-16328

CVE.ORG link : CVE-2026-16328

JSON object : View

Products Affected

No product.

CWE

CWE-918

Server-Side Request Forgery (SSRF)

{"id": "CVE-2026-16328", "cveTags": [], "metrics": {"ssvcV203": [{"source": "134c704f-9b21-4f2e-91b3-4a467353bcc0", "ssvcData": {"id": "CVE-2026-16328", "role": "CISA Coordinator", "options": [{"exploitation": "none"}, {"automatable": "yes"}, {"technicalImpact": "partial"}], "version": "2.0.3", "timestamp": "2026-07-29T19:10:50.793675Z"}}], "cvssMetricV31": [{"type": "Secondary", "source": "security@hashicorp.com", "cvssData": {"scope": "CHANGED", "version": "3.1", "baseScore": 8.6, "attackVector": "NETWORK", "baseSeverity": "HIGH", "vectorString": "CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:N/A:N", "integrityImpact": "NONE", "userInteraction": "NONE", "attackComplexity": "LOW", "availabilityImpact": "NONE", "privilegesRequired": "NONE", "confidentialityImpact": "HIGH"}, "impactScore": 4.0, "exploitabilityScore": 3.9}]}, "affected": [{"source": "security@hashicorp.com", "affectedData": [{"repo": "https://github.com/hashicorp/consul-mcp-server", "vendor": "HashiCorp", "product": "Tooling", "versions": [{"status": "affected", "version": "0.1.0", "lessThan": "0.1.4", "versionType": "semver"}], "platforms": ["64 bit", "32 bit", "x86", "ARM", "MacOS", "Windows", "Linux"], "defaultStatus": "unaffected"}]}], "published": "2026-07-29T19:16:45.060", "references": [{"url": "https://discuss.hashicorp.com/t/hcsec-2026-24-multiple-vulnerabilities-impacting-hashicorp-consul-mcp-server/77612", "source": "security@hashicorp.com"}], "vulnStatus": "Deferred", "weaknesses": [{"type": "Secondary", "source": "security@hashicorp.com", "description": [{"lang": "en", "value": "CWE-918"}]}], "descriptions": [{"lang": "en", "value": "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."}, {"lang": "es", "value": "En consul-mcp-server, las versiones 0.1.0 hasta la 0.1.3 no restring\u00edan c\u00f3mo se suministraba la direcci\u00f3n del backend de Consul, permitiendo a un cliente conectado anular la direcci\u00f3n de Consul configurada del servidor a trav\u00e9s de una cabecera de solicitud. Esto puede permitir a un cliente malicioso redirigir el tr\u00e1fico de la API de Consul del servidor a un endpoint controlado por un atacante, potencialmente exfiltrando el token de Consul configurado en el servidor. Esta vulnerabilidad, CVE-2026-16328, est\u00e1 corregida en consul-mcp-server 0.1.4."}], "lastModified": "2026-10-24T13:10:00.147", "sourceIdentifier": "security@hashicorp.com"}