CVE-2026-134803

DBHub before 1.7.0 Read-Only Mode Bypass via Backslash-Escaped Quotes

Published Nov 22, 2026 CVSS 4.0 · 7.2 High EPSS n/a KEV · Not listed
Description
DBHub before 1.7.0 contains a read-only mode bypass vulnerability that allows MCP clients restricted to readonly execute_sql to run write and DDL statements via backslash-escaped quotes. Attackers can hide stacked statements that clear transaction_read_only or COMMIT inside strings misparsed by scanSingleQuotedString, letting them modify or drop MySQL, MariaDB, or PostgreSQL data.

Analysis

AI-generated

Technical impact

The vulnerability in DBHub allows attackers to bypass the read-only mode by injecting backslash-escaped quotes into SQL strings. The parser misinterprets these escaped sequences during the scanSingleQuotedString operation, enabling the execution of write or DDL statements that should be prohibited. As a result, unauthorized modifications, deletions, or schema changes can occur against MySQL, MariaDB, or PostgreSQL data, compromising the integrity of the database. This flaw is classified as CWE-436, which denotes improper escaping of characters.

Affected Systems

Bytebase DBHub versions prior to 1.7.0 are affected. The issue has been observed in release 1.6.1 and earlier built for MySQL, MariaDB, and PostgreSQL connections. Users of these older releases are at risk if their MCP clients are allowed to issue execute_sql commands while configured for read-only access.

Risk and Exploitability

The CVSS score of 7.2 indicates a moderate to high severity. EPSS information is not available, so the likelihood of exploitation cannot be quantified. The vulnerability is not listed in CISA KEV. Attackers must possess the ability to run SQL via an MCP client; the likely entry point is the execute_sql command, which, when combined with the bypass, enables executing additional statements disguised within string literals. Because the flaw manipulates the parsing of quoted strings, it can be triggered without elevated privileges on the database itself, providing a path for data tampering or loss.

Remediation

No solution or workaround provided in the CVE record.

OpenCVE Recommended Actions

  • Upgrade to DBHub v1.7.0 or later, where the parse bug is fixed.
  • Restrict MCP clients to strict read-only permissions and disallow execute_sql for users that do not require write access.
  • Sanitize and escape backslashes in user-provided SQL, ensuring that strings cannot be interpreted as containing executable statements.

Generated by OpenCVE AI on November 22, 2026 at 22:23 UTC.

Tracking

Sign in to view the affected projects.

Advisories

No advisories available
History
Type Values Removed Values Added
Description DBHub before 1.7.0 contains a read-only mode bypass vulnerability that allows MCP clients restricted to readonly execute_sql to run write and DDL statements via backslash-escaped quotes. Attackers can hide stacked statements that clear transaction_read_only or COMMIT inside strings misparsed by scanSingleQuotedString, letting them modify or drop MySQL, MariaDB, or PostgreSQL data.
Title DBHub before 1.7.0 Read-Only Mode Bypass via Backslash-Escaped Quotes
Weaknesses CWE-436
References
Metrics cvssV3_1

{'score': 8.1, 'vector': 'CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H'}

cvssV4_0

{'score': 7.2, 'vector': 'CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:N'}

Subscriptions

No data.

Weaknesses

Sources

Status
PUBLISHED
Assigner
VulnCheck
Published
Updated
Nov 22, 2026, 9:22 PM
Reserved
Nov 22, 2026, 5:09 PM
Status
Deferred
Published
Nov 22, 2026, 10:17 PM
Modified
Nov 22, 2026, 10:17 PM