DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

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 · score source

EPSS

• CVE-2026-61742: 0.20% estimated exploitation activity in the next 30 days; percentile 10.00 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

Summary DBHub 0.21.2 exposes 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…

Published by the source

24 Sep 2026, 19:36 UTC

Last modified by the source

24 Sep 2026, 19:45 UTC

Source last checked

26 Oct 2026, 13:02 UTC

1. Revision 4 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-fm8p-53ww-hf6w

2. Revision 3 · amended · 24 Oct 2026

   Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.

3. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GHSA-fm8p-53ww-hf6w

4. Revision 1 · created · 23 Oct 2026

   Published from ghsa record GHSA-fm8p-53ww-hf6w

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61742

Advisory: DBHub HTTP transport DNS rebinding allows unauthenticated browser-origin SQL execution
IDs: CVE-2026-61742, GHSA-fm8p-53ww-hf6w
Record: https://patchnext.com/advisories/cve-2026-61742 (revision 4, source checked 26 Oct 2026, 13:02 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 9.3)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @bytebase/dbhub 0.22.5. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @bytebase/dbhub: affected <= 0.22.4; fixed in 0.22.5

## Suggested inspection (read-only)
- `npm ls @bytebase/dbhub --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @bytebase/dbhub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-fm8p-53ww-hf6w (GitHub-reviewed advisory GHSA-fm8p-53ww-hf6w lists affected ranges: npm @bytebase/dbhub >=0 <=0.22.4)
- Verified: https://osv.dev/vulnerability/GHSA-fm8p-53ww-hf6w (OSV record GHSA-fm8p-53ww-hf6w lists affected ranges: npm @bytebase/dbhub >=0 <0.22.5 (fixed))

Commands are suggestions: review each one before running it.