CVE-2026-61788
Published:September 24, 2026
Updated:October 09, 2026
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.
Affected Packages
@bytebase/dbhub (NPM):
Affected version(s) >=0.0.1 <0.22.6Fix Suggestion:
Update to version 0.22.6Related Resources (7)
Do you need more information?
Contact UsCVSS v4
Base Score:
9.1
Attack Vector
NETWORK
Attack Complexity
HIGH
Attack Requirements
NONE
Privileges Required
NONE
User Interaction
NONE
Vulnerable System Confidentiality
HIGH
Vulnerable System Integrity
HIGH
Vulnerable System Availability
NONE
Subsequent System Confidentiality
NONE
Subsequent System Integrity
NONE
Subsequent System Availability
NONE
CVSS v3
Base Score:
7.4
Attack Vector
NETWORK
Attack Complexity
HIGH
Privileges Required
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
HIGH
Integrity
HIGH
Availability
NONE
Weakness Type (CWE)
EPSS
Base Score:
0.30