CVE-2026-61742 Details

A vulnerability in DBHub versions prior to 0.22.5 allows for unauthenticated access to an HTTP MCP endpoint via DNS rebinding. When DBHub is started with the HTTP transport mode, the server checks that the 'Origin' hostname matches the 'Host' hostname. However, this check does not prevent DNS rebinding attacks. An attacker can manipulate DNS to have a hostname resolve to the victim's DBHub server, making both the 'Origin' and 'Host' headers appear as the attacker-controlled hostname. This bypasses the origin validation and allows the attacker to invoke DBHub MCP tools from the victim's browser. In the default demo configuration, this could read and write to the demo SQLite database. In real-world scenarios, the impact would depend on the database and DBHub's tool permissions.

Users can update to DBHub version 0.22.5 or later, and bind the HTTP transport to '127.0.0.1' by default, requiring explicit opt-in for non-loopback hosts. Additionally, an allowed-hosts policy should be implemented to reject arbitrary 'Host' values, and an allowed-origins policy to prevent the reflection of arbitrary origins by default. It is also recommended to require an authentication token or similar capability before processing MCP requests over HTTP.