Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-61742

Vulnerability in @bytebase/dbhub (CVE-2026-61742)

Summary

Vulnerability in @bytebase/dbhub (CVE-2026-61742). Risk of unauthorized operations or information disclosure. Exploitable via Host header. Mitigation: upgrade to 0.22.5 or later.

Original description

The description as published by the source.

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 permissions and database credentials.

Recommended severity: High. It may become Critical when HTTP transport is connected to production or broadly privileged database credentials.

Details

Affected target:

  • Package: @bytebase/dbhub
  • Version tested: 0.21.2
  • Repository commit tested: 72adfdcf7bcfe46b25edbc776ce096006eba9b02
  • Affected mode: HTTP transport (--transport http)
  • Default package transport: stdio
  • Not affected by this specific browser-origin vector: s…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-61742 has been found in @bytebase/dbhub.
Attackers can target a specific entry point like Host header over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade @bytebase/dbhub to 0.22.5 or later.
If unsure, ask your IT team or search "@bytebase/dbhub CVE-2026-61742" on the vendor's site.

CVE-2026-61742 (@bytebase/dbhub) — CWE-306
Attack surface: Host header / Origin / Host / req.headers.origin
Patched: 0.22.5 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in @bytebase/dbhub. Attackers reach the vulnerable code path via Host header.

📍 Affected scope

Check the vendor advisory for the affected versions of @bytebase/dbhub. Attack surface: Host header / Origin / Host / req.headers.origin.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 0.22.5.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r '@bytebase/dbhub' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r '@bytebase/dbhub' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で @bytebase/dbhub を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch 
    Upgrade @bytebase/dbhub to 0.22.5

    ステージング環境で 0.22.5 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

npm @bytebase/dbhub
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"0.22.5"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details