CVE-2026-61742 · GHSA-fm8p-53ww-hf6w
DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution
- Risk score
- 68/100
- CVSS
- 9.3 v4.0
- Exploit chance (30 days)
- 0.2%
- Published
- 24 Sep 2026
Open in the live forecast Today's forecast
What to know
- What it is
- 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 chec…
- Affected
- @bytebase/dbhub (npm) <= 0.22.4
- Fix
- Upgrade @bytebase/dbhub to 0.22.5 or later.
- Exploitation
- No known exploitation
Story map
At a glance
@bytebase/dbhub: Amber, patch this week. 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 chec…
The flaws
- CVE-2026-61742: DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution (CVSS 9.3 · EPSS 0%)
- CVE-2026-61788: @bytebase/dbhub's read-only mode does not prevent database writes (CVSS 7.4 · EPSS 0%)
- GHSA-j656-3hf2-fvjc: DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation (CVSS 6.1)
The fix
Upgrade @bytebase/dbhub: 0.22.5 · 0.22.6 or later on your release line
Who is exposed: @bytebase/dbhub (npm) <= 0.22.4
Where it stands
- Public proof of concept
Connects to
- Same weakness: Missing authentication (CWE-306). 371 other warnings in 30 days
Why it is Amber
- CVSS 9.3 critical
- Remotely exploitable without logging in
- On your watchlist: npm
Affected packages
| Package | Ecosystem | Vulnerable | Fixed in |
|---|---|---|---|
| @bytebase/dbhub | npm | <= 0.22.4 | 0.22.5 |
References
- https://github.com/advisories/GHSA-fm8p-53ww-hf6w
- https://github.com/bytebase/dbhub/security/advisories/GHSA-fm8p-53ww-hf6w
- https://nvd.nist.gov/vuln/detail/CVE-2026-61742
- https://github.com/bytebase/dbhub/pull/340
- https://github.com/bytebase/dbhub/commit/5bf5c3242a22e94871dfdf53913c84a5025b7381
- https://github.com/bytebase/dbhub/releases/tag/v0.22.6
- https://github.com/advisories/GHSA-fm8p-53ww-hf6w
Original 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.
Last activity 24 Sep 2026. Patch Forecast updates every hour.