Model Context Protocol Allows DNS Rebinding Due to Origin Header Validation Failure
Default status is the baseline for the product, each version can override it (e.g. patched versions marked unaffected).
| Vendor | Product | Default status | Versions | ||||||
|---|---|---|---|---|---|---|---|---|---|
| MCP Toolbox for Databases | unaffected |
|
No data.
No data.
| Vendor | Product | Versions | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|
| Mcp Toolbox For Databases |
|
| Source | ID | Title |
|---|---|---|
Github GHSA |
GHSA-76g7-m3xw-x9gr | MCP Toolbox for Databases has an Origin Validation Error |
No CVSS v3.1
No CVSS v3.0
No CVSS v2
This CVE is not in the KEV list.
Exploit prediction score: < 1% (0.219% probability within 30 days)
| Type | Values Removed | Values Added |
|---|---|---|
| Metrics |
ssvc
|
| Type | Values Removed | Values Added |
|---|---|---|
| Title | Model Context Protocol Allows DNS Rebinding Due to Origin Header Validation Failure |
| Type | Values Removed | Values Added |
|---|---|---|
| First Time appeared |
Google
Google mcp Toolbox For Databases |
|
| Vendors & Products |
Google
Google mcp Toolbox For Databases |
| Type | Values Removed | Values Added |
|---|---|---|
| Description | 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. | |
| Weaknesses | CWE-346 | |
| References |
| |
| Metrics |
cvssV4_0
|