CVE-2026-81092
Description
A flaw was found in mcp-go. This component failed to validate the Host header in HTTP requests, specifically within its StreamableHTTPServer and SSEServer transports. A remote attacker could exploit this by using a crafted web page to perform a DNS rebinding attack. This allows the attacker to direct a controlled domain name to the loopback address, bypassing local network restrictions. Consequently, the attacker could access and interact with local services and resources, potentially leading to information disclosure or unauthorized actions.
Statement
DNS rebinding requires a web browser executing JavaScript to run on the same host as the mcp-go HTTP server, with the user visiting a malicious page during that window. Red Hat products carrying this dependency are containerized server-side services (tempo, mcp-gateway) and CLI tools (rhai-cli) deployed in Kubernetes/OpenShift environments. In those deployments no browser shares the loopback interface with the affected service, so the preconditions for exploitation are not met. The high confidentiality and integrity scores in the CVSS vector reflect what a running mcp-go server can expose if the attack succeeds; in Red Hat deployments the co-located browser condition does not arise in normal operations.
Mitigation
Where an immediate update to mcp-go v0.56.0 is not possible: restrict inbound connections to known trusted clients via network policy or firewall rules, and place a reverse proxy in front of the MCP endpoint that enforces strict Host header validation.
Common Vulnerability Scoring System (CVSS) Score Details
Info alert:Important note
CVSS scores for open source components depend on vendor-specific factors (e.g. version or build chain). Therefore, Red Hat's score and impact rating can be different from NVD and other vendors. Red Hat remains the authoritative CVE Naming Authority (CNA) source for its products and services (see Red Hat classifications).
CVSS v3 Score Breakdown
| Red Hat | NVD | cve.org | |
|---|---|---|---|
| Base Score | 6.8 | N/A | 6.8 |
| Attack Vector | Network | N/A | Network |
| Attack Complexity | High | N/A | High |
| Privileges Required | None | N/A | None |
| User Interaction | Required | N/A | Required |
| Scope | Unchanged | N/A | Unchanged |
| Confidentiality | High | N/A | High |
| Integrity Impact | High | N/A | High |
| Availability Impact | None | N/A | None |
Vector
Red Hat: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
cve.org: CVSS:3.1/AV:N/AC:H/PR:N/UI:R/S:U/C:H/I:H/A:N
Understanding the Weakness (CWE)
Confidentiality
Technical Impact: Read Application Data
Integrity
Technical Impact: Execute Unauthorized Code or Commands
Access Control
Technical Impact: Bypass Protection Mechanism
By providing URLs to unexpected hosts or ports, attackers can make it appear that the server is sending the request, possibly bypassing access controls such as firewalls that prevent the attackers from accessing the URLs directly. The server can be used as a proxy to conduct port scanning of hosts in internal networks, use other URLs such as that can access documents on the system (using file://), or use other protocols such as gopher:// or tftp://, which may provide greater control over the contents of requests.
Frequently Asked Questions
Not sure what something means? Check out our Security Glossary.
Want to get errata notifications? Sign up here.
