The vulnerability involves the Model Context Protocol's lack of origin host validation prior to MCP Toolbox for Databases v0.25.0, allowing potential DNS rebinding attacks. The introduction of the "--allowed-hosts" flag in v0.25.0 allows users to specify permitted hosts at server startup, complementing the "--allowed-origins" flag. Both flags default to "*", maintaining backward compatibility but warning users about security risks. Documentation updates emphasize these security considerations. No official remediation level or patch is indicated in the advisory, and no affected versions are explicitly stated.

The vulnerability can allow attackers to bypass origin validation, potentially enabling DNS rebinding attacks that compromise server security. The CVSS 4.0 score of 9.4 indicates a critical severity with high impact on confidentiality, integrity, and availability. However, no known exploits are reported in the wild. The lack of strict origin validation prior to v0.25.0 means deployments using default configurations may be vulnerable.

Users should upgrade to MCP Toolbox for Databases version 0.25.0 or later and configure the "--allowed-hosts" and "--allowed-origins" flags to specify permitted hosts and origins explicitly rather than using the default "*" wildcard. The server outputs a startup warning if either flag is set to "*", prompting administrators to tighten access controls. No official patch or remediation level is provided, so following the configuration guidance and upgrading to the version with these flags is the recommended mitigation.