# 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.

- **Severity:** Critical 9.3 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Sep 2026
- **Updated:** 24 Sep 2026
- **Also known as:** GHSA-fm8p-53ww-hf6w

## 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.

Weakness: CWE-346 (Origin Validation Error), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-61742?

2 open source packages ship an affected version, including @bytebase/dbhub.


| Package | Ecosystem | 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.

## Is CVE-2026-61742 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61742 exists.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-61742 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-61742 exists.

Affected packages and fixed versions:
- @bytebase/dbhub (npm): affected all versions; fixed in 0.22.5
- @bytebase/dbhub (npm): affected all versions; fixed in 0.22.5

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-61742/ (Markdown: https://insights.sbomify.com/CVE-2026-61742/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-61742
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-61742
- OSV: https://osv.dev/vulnerability/CVE-2026-61742

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-61742/
Summaries are generated and may contain mistakes; the official description above is the record.