@bytebase/dbhub's read-only mode does not prevent database writes (CVE-2026-61788) | HOL Guard CVE

High · CVSS 7.4CVE-2026-61788GHSA-MWWR-P57H-56PF

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

Answer in brief

CVE-2026-61788 records a High severity (CVSS 7.4) vulnerability in @bytebase/dbhub's read-only mode does not prevent database writes. The current sources do not mark it as known exploited. The current feed maps bytebase/dbhub (generic), @bytebase/dbhub (npm). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Sep 24, 2026Updated Sep 24, 2026Source checked Sep 25, 2026First seen by HOL Sep 25, 2026Material review Sep 24, 2026

Upstream Advisory

Key facts

Risk: High · CVSS 7.4
Exploitation: Not marked as known exploited
Affected software: 2 mapped packages or products
Fix availability: Available

Why this deserves its current priority

CVSS is 7.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps bytebase/dbhub (generic), @bytebase/dbhub (npm). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
Package	Affected range	Fixed version
bytebase/dbhubgeneric	<0.22.6	0.22.6
@bytebase/dbhubnpm	<0.22.6	0.22.6

Recommended response

Check inventory. Check lockfiles and deployed manifests for bytebase/dbhub, @bytebase/dbhub.
Review the reported fix. Update bytebase/dbhub to 0.22.6; @bytebase/dbhub to 0.22.6 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

Published upstream
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
Source modified
Sep 24, 2026
Evidence: source:cvelist:source_dates:source-dates:record
First seen by HOL
Sep 25, 2026

Sources and claim methodology

Upstream source description

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.

Quoted source text, attributed separately from HOL analysis.