CVE-2026-61788: bytebase dbhub advisory

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. Prior to version 0.22.6, setting `readonly = true` on the `execute_sql` tool does not make the connection read-only. The connectors are written to set PostgreSQL `default_transaction_read_only=on` (and open SQLite in `readOnly` mode), but that code is gated on a config value that is never populated, so it never runs. The only thing left enforcing read-only is a classifier that inspects the first keyword of each statement. Any `SELECT` that writes or has side effects through a function call passes it. With an ordinary role this allows sequence tampering; with a privileged role it allows writing arbitrary files on the server (`lo_export`), reading arbitrary host files (`pg_read_file`), and remote code execution (`dblink` + `COPY ... TO PROGRAM`). The HTTP transport is unauthenticated and binds to `0.0.0.0` by default, so this is reachable by any network caller of `/mcp`. Version 0.22.6 patches the issue.

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

Weakness: CWE-184: Incomplete List of Disallowed Inputs; CWE-636: Not Failing Securely (‘Failing Open’); CWE-863: Incorrect Authorization

How it can be exploited

Exploitable over the network with high attack complexity needing no privileges and no user interaction. Impact: confidentiality high, integrity high, availability none. CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N

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

Public exploit evidence (Exploit Observer)

Exploit Observer found 3 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 8 references on Exploit Observer

Live scores

EPSS: 0.004
low predicted chance of attack
VEDAS: 0.986
strong exploit evidence
On CISA KEV: Not listed
Detection rule: Suricata

Who is affected

Product	Affected	Not affected
bytebase dbhub	version < 0.22.6	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

Suricata rules (network detection)

1 rule that alert on traffic matching this exploit: VEDAS CVE-2026-61788 DBHub - Read-Only Enforcement Bypass. Add them to your Suricata rule set and reload.

Show the rules

suricata

alert http $EXTERNAL_NET any -> $HTTP_SERVERS $HTTP_PORTS (msg:"VEDAS CVE-2026-61788 DBHub - Read-Only Enforcement Bypass"; flow:established,to_server; http.method; content:"POST"; http.uri; content:"/mcp"; nocase; http.request_body; content:"execute_sql"; nocase; fast_pattern; content:"tools/call"; nocase; classtype:web-application-attack; reference:cve,CVE-2026-61788; reference:url,https://www.exploit.observer/?keyword=CVE-2026-61788&match=exact; reference:url,https://subdomain.center/?engine=ammonites&keyword=dbhub&match=exact; sid:1092402; rev:1;)

CVE-2026-61788.rules on GitHub

References

Other references

https://github.com/bytebase/dbhub/security/advisories/GHSA-mwwr-p57h-56pf (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.