CVE-2026-61742 DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution
Attackers can use DNS rebinding to execute SQL commands via the HTTP transport, allowing unauthorized database access.
- Exploited in the wild
- Not known
- Login needed
- Not needed
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-61742?
CVE-2026-61742 is a critical server-side request forgery vulnerability in bytebase dbhub, published on 24 Sep 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Official description
DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite. Versions prior to 0.22.5 expose an unauthenticated HTTP MCP endpoint when started with the documented HTTP transport mode, for example `--transport http --port 8080`. The HTTP server attempts to protect browser-origin access by checking whether the `Origin` hostname equals the `Host` hostname, then reflecting the validated `Origin` into `Access-Control-Allow-Origin`. This does not stop DNS rebinding. After an attacker-controlled hostname rebinds to a victim-accessible DBHub HTTP server, both `Origin` and `Host` can contain the attacker-controlled hostname, so DBHub accepts the request and dispatches MCP tool calls. As a result, a malicious website can deterministically invoke DBHub MCP tools from the victim's browser without prompt injection or model involvement. With the default demo configuration this can read and write the demo SQLite database; with a real configured database, the same primitive can read, enumerate, and potentially write database contents depending on DBHub's configured tool permissions and database credentials. Version 0.22.5 fixes the issue.
Which versions are affected by CVE-2026-61742?
2 open source packages ship an affected version, including @bytebase/dbhub.
| Package | Affected | Fixed in |
|---|---|---|
@bytebase/dbhub npm | All versions | 0.22.5 |
@bytebase/dbhub npm | All versions | 0.22.5 |
How do I fix CVE-2026-61742?
Upgrade @bytebase/dbhub to 0.22.5 or later.
Upgrade, and send outbound requests through an allow-list that blocks internal addresses. More about Server-side request forgery.
Is CVE-2026-61742 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61742 exists.
Sources
Also known as GHSA-fm8p-53ww-hf6w.