MCP Toolbox for Databases has an Origin Validation Error
Google MCP Toolbox for Databases
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/googleapis/mcp-toolbox Go |
|
|
| github.com/googleapis/genai-toolbox Go |
|
|
Google MCP Toolbox for Databases
| Product | Affected | Fixed in |
|---|---|---|
| github.com/googleapis/mcp-toolbox Go |
|
|
| github.com/googleapis/genai-toolbox Go |
|
|
The Model Context Protocol has a security warning advising servers to validate the "Origin" header on all incoming connections to prevent DNS rebinding attacks. Prior to the v0.25.0 release, users had no way to validate the origin's host. In v0.25.0, a new "--allowed-hosts" flag was introduced alongside the existing "--allowed-origins" flag, enabling users to specify permitted hosts at server startup. Both flags default to "*", allowing users to implement strict access controls as needed without breaking existing setups. If either flag is set to "*", the server will output a startup warning about potential vulnerabilities. Documentation has also been updated to highlight these security considerations.
From the CVE record · Google
Before v0.25.0, the server provided no way to validate an incoming connection’s origin host, leaving it exposed to potential DNS rebinding attacks. Version 0.25.0 adds host validation controls, but both host and origin allowlists default to unrestricted (`*`). The input does not specify authentication or user-interaction requirements.
Teams using the Go packages github.com/googleapis/mcp-toolbox or github.com/googleapis/genai-toolbox before 0.25.0 should check their deployments.