DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation

The read-only mode can be bypassed on the MySQL and MariaDB connectors. In read-only mode a caller can still execute arbitrary write and DDL statements for example DROP TABLE, which defeats the protection that read-only mode is meant to provide when a database is exposed to an AI agent. Root caus...

GHSA-J656-3HF2-FVJC DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation

The read-only mode can be bypassed on the MySQL and MariaDB connectors. In read-only mode a caller can still execute arbitrary write and DDL statements for example DROP TABLE, which defeats the protection that read-only mode is meant to provide when a database is exposed to an AI agent. Root caus...

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 on the MySQL and MariaDB connectors. In src/utils/sql-parser.ts, scanSingleLineComment treats every double dash as a comment start, whereas MySQL and...

CVE-2026-61789 DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation

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...

CVE-2026-61789 DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation

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...

CVE-2026-61789

DBHub, a database MCP server, contains a vulnerability in its MySQL and MariaDB connectors prior to version 0.22.6 . The root cause is an interpretation conflict in src/utils/sql-parser.ts, where scanSingleLineComment incorrectly treats every double dash (--) as a comment start, unlike the actual...

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 on the MySQL and MariaDB connectors. In "src/utils/sql-parser.ts", "scanSingleLineComment" treats every double dash as a comment start, whereas MySQL...

EUVD-2026-114181

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...

PT-2026-133679

Name of the Vulnerable Software and Affected Versions DBHub versions prior to 0.22.6 Description Read-only SQL validation can be bypassed on the MySQL and MariaDB connectors. The scanSingleLineComment function in src/utils/sql-parser.ts incorrectly treats every double dash as the start of a...

CVE-2026-61789: bytebase dbhub: DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite

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...

CVE-2026-79536

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

CVE-2026-79536

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

EUVD-2026-89363

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

CVE-2026-79536

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

PT-2026-102819

Name of the Vulnerable Software and Affected Versions bytebase dbhub version 1.2.0 Description An issue exists in the /utils/sql-parser.ts component that allows attackers to access sensitive database information by using a crafted SQL statement. This is a SQL injection, which occurs when an...

CVE-2026-79536

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

CVE-2026-79536

The bytebase dbhub v1.2.0 software contains a SQL injection vulnerability within the /utils/sql-parser.ts component. An attacker can exploit this flaw by submitting a crafted SQL statement to gain unauthorized access to sensitive database information . No specific remediation steps or exploit det...

CVE-2026-79536: Improper Neutralization of Special Elements used in an SQL Command

bytebase dbhub v1.2.0 was discovered to contain a SQL injection vulnerability in the /utils/sql-parser.ts component. This vulnerability allows attackers to access sensitive databse information via a crafted SQL statement...

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

Summary Setting readonly = true on the executesql tool does not make the connection read-only. The connectors are written to set PostgreSQL defaulttransactionreadonly=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...

GHSA-MWWR-P57H-56PF @bytebase/dbhub's read-only mode does not prevent database writes

Summary Setting readonly = true on the executesql tool does not make the connection read-only. The connectors are written to set PostgreSQL defaulttransactionreadonly=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...