CVE-2026-61789: DBHub, a database Model Context Protocol (MCP) server, lets SQL that hides a write behind a double dash pass its read-only check on MySQL and MariaDB
The National Vulnerability Database (NVD) record says that before 0.22.6, DBHub's read-only validation can be bypassed on its MySQL and MariaDB connectors, so anyone able to influence the assistant's SQL, including through prompt injection in content the assistant reads, can modify or drop database data, subject to the database account's privileges; fixed in 0.22.6.
The record
- Kind
- Vulnerability
- Source record
- CVE-2026-61789: DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite. Prior to 0.22.6, read-only SQL validation can be bypassed (National Vulnerability Database record)
- Record published
- 2026-10-30
- Posted here
- 2026-10-31
- World
- Software agents · Enterprise work agents
- Controls concerned
- Retrieved content as data C-I1; Destructive-action gate C-E3
- Checked
- Checked against its record on 2026-10-31 by a reader who did not draft it; report
verification/reports/SIG-2026-10-31-012-2026-10-31.md.
A signal's controls are the ones its record points at, the exposure; a case's controls are the ones its records show were absent or failed, so the two can differ.
What a signal is. A signal records what a primary record says; it assigns no fault. It is lighter than a case: one dated item from one record, tagged with the world, sector and controls it touches. It becomes a case when it meets the bar for one.
New signals like this, once a week. A short email when a case, signal or rule touches software agents. Free; unsubscribe in one click.
Get the weekly email