PoC Monitor
← All CVEs
CVE-2026-61788published 24 Sep 2026 17:37 UTCData: JSON · API

Bytebase dbhub

@bytebase/dbhub's read-only mode does not prevent database writes

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.

First public PoC None yetno public PoC found
Public PoCs00 on GitHub
CVSS7.4high · scored by CNA · CWE-184
CISA KEV Not listednot known exploited

Affected versions and mitigation

From the CVE record and the vendor's references.

Affected

bytebase dbhub
  • < 0.22.6

Fixed in 0.22.6

Mitigation

Upgrade dbhub to 0.22.6 or later.

References

Timeline

Days relative to CVE publication
-2t=0+2+4+6+8CVE published24 Sep 2026 · t = 0

No public PoC found yet; not in CISA KEV.

PoC repositories

Found on GitHub.

No PoC repositories found yet.