CVE-2026-61789

6.1 MEDIUM 0.4% exploit odds Fix listed Injection Server

What it is

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 on the MySQL and MariaDB connectors. In `src/utils/sql-parser.ts`, `scanSingleLineComment` treats every double dash as a comment start, whereas MySQL and MariaDB require following whitespace, a control character, or the end of the line. The read-only check in `src/tools/execute-sql.ts` validates split statements with `isReadOnlySQL`, but `src/connectors/mysql/index.ts` and `src/connectors/mariadb/index.ts` execute the original string with `multipleStatements` enabled. A double dash followed by a non-whitespace character can therefore hide a subsequent write or destructive DDL statement from the validator while the database interprets the dashes as minus operators and executes both statements. Anyone able to influence the assistant's SQL, including through prompt injection in content the assistant reads, can bypass read-only mode to modify or drop database data, subject to the database account's privileges. PostgreSQL is not affected by this path because its double-dash parsing agrees with the checker and its connector executes individual split statements. This issue is fixed in version 0.22.6.

At a glance

Exploitability: Can be exploited over the network without logging in, but needs a user to act. High risk of data tampering, service disruption.
Exploit odds: 0.4% chance of exploitation in the next 30 days (EPSS).
Fix: A patch, advisory or fixed version is referenced. Upgrade or apply it.

Timeline

2026-10-30 17:17 UTC PublishedDisclosed publicly on CVE.org and NVD
2026-10-30 17:17 UTC Last updatedMost recent change to the record

Why it ranks here

Exploited in the wild: no, CISA does not list it.
Exploit odds: 0.4% in the next 30 days (EPSS).
Severity: 6.1 MEDIUM (CVSS).
Fix: a patch or advisory is linked.

Details

Published: 2026-10-30 17:17 UTC
Last modified: 2026-10-30 17:17 UTC
Exploit probability: 0.4% · EPSS, next 30 days
Weakness: CWE-436
Record status: Deferred

Attack profile CVSS 4.0 · 6.1

Attack vector: Network
Complexity: Low
Attack requirements: Present
Privileges needed: None
User interaction: Passive
Confidentiality: None
Integrity: High
Availability: High

Raw vector

CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:P/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X

Is it in your code?

Hand this to your coding agent. It searches your project for the affected products and checks versions. Nothing leaves your machine.

Read https://cve-list.com/agent/cve/CVE-2026-61789.md and follow it. Check whether this project is affected by CVE-2026-61789. Read only. Don't change anything and don't upload my code. Tell me yes, no or not sure, with the file as proof.

· More options · Status badge

Download Square Reddit

Fix and advisories

References

NVD record · CVE.org record