CVE-2026-61742: bytebase dbhub vulnerability

Advisory generated from the CVE record, CISA, Exploit Observer and VEDAS: what it is, whether it is exploited, who is affected, and how to fix and detect it.

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

Description quoted from the CVE record (assigned by GitHub_M, published 2026-09-24).

Weakness: CWE-306: Missing Authentication for Critical Function; CWE-346: Origin Validation Error

How it can be exploited

Exploitable over the network with low attack complexity with no special attack requirements needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability high. 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

CISA assessment (SSVC): CISA assesses that a public proof of concept exists. Automatable: yes. Technical impact: total.

Public exploit evidence (Exploit Observer)

Exploit Observer found 2 code repositories naming this CVE.

Code repositories that name a CVE are often scanners, copies or fakes, and some are malware. Read the code before running anything.

See all 6 references on Exploit Observer

Live scores

EPSS: 0.002
low predicted chance of attack
VEDAS: 0.988
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Nuclei

Who is affected

Product	Affected	Not affected
bytebase dbhub	version < 0.22.5	Not stated

Version ranges exactly as the CVE record states them. “Before X” means X is the first fixed version.

How to fix it

No fixed version or vendor advisory is listed in the CVE record yet. Watch the vendor’s security page.

How to detect it

Nuclei template (active check)

DBHub - Unauthenticated MCP Endpoint Exposure
DBHub (a database MCP server) prior to 0.22.5 exposes an unauthenticated HTTP MCP endpoint at POST /mcp when started with the documented HTTP transport mode (e.g. --transport http). The endpoint requires no authentication and, because its only browser protection is an Origin/Host equality check, a direct JSON-RPC request with no Origin header is accepted and dispatched. This template sends a JSON-RPC initialize request and confirms an exposed DBHub MCP server by matching the serverInfo handshake.

Name and description quoted from the template, written by VEDAS.

The template sends 1 request (POST /mcp); it decides using regex, word matchers. Severity in the template: critical. Marked as not yet verified against a live vulnerable target.

Run it against a host you own or are authorised to test:

bash

nuclei -u https://your-host -t CVE-2026-61742.yaml

Show the template (47 lines)

yaml

id: CVE-2026-61742

info:
  name: "DBHub - Unauthenticated MCP Endpoint Exposure"
  author: vedas-arpsyndicate
  severity: critical
  description: |
    DBHub (a database MCP server) prior to 0.22.5 exposes an unauthenticated HTTP MCP endpoint at POST /mcp
    when started with the documented HTTP transport mode (e.g. --transport http). The endpoint requires no
    authentication and, because its only browser protection is an Origin/Host equality check, a direct
    JSON-RPC request with no Origin header is accepted and dispatched. This template sends a JSON-RPC
    initialize request and confirms an exposed DBHub MCP server by matching the serverInfo handshake.
  reference:
    - https://www.exploit.observer/?keyword=CVE-2026-61742&match=exact
    - https://subdomain.center/?engine=ammonites&keyword=dbhub&match=exact
  classification:
    cvss-metrics: 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
    cvss-score: 9.3
    cve-id: CVE-2026-61742
    cwe-id: CWE-306
  metadata:
    verified: false
  tags: cve,cve2026,dbhub,mcp,exposure

http:
  - raw:
      - |
        POST /mcp HTTP/1.1
        Host: {{Hostname}}
        Content-Type: application/json
        Accept: application/json, text/event-stream

        {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"vedas","version":"1.0"}}}

    matchers-condition: and
    matchers:
      - type: word
        part: body
        words:
          - 'serverInfo'
          - 'protocolVersion'
          - 'jsonrpc'
        condition: and
      - type: regex
        part: body
        regex:
          - '(?i)dbhub'

CVE-2026-61742.yaml on GitHub

References

Other references

https://github.com/bytebase/dbhub/security/advisories/GHSA-fm8p-53ww-hf6w (x_refsource_CONFIRM)

Other databases

Where this comes from

This advisory is generated automatically by VEDAS from: CVE.org record, cve-scores (EPSS and VEDAS), Exploit Observer, vedas-signatures. Text in quotes is reproduced from the source; everything else is a fixed template filled with source fields. Nothing here is written by a language model. Check the vendor advisory before acting, and read how VEDAS and Exploit Observer work, and their limits.