Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

New CVE Detected

CVE-2026-79536 – SQL Injection / Read-Only Mode Bypass – DBHub (bytebase/dbhub) v1.2.0 and Earlier

Be the first to know when new zero-days emerge:

Summary

CVE-2026-79536 is a critical SQL injection (CWE-89) vulnerability in DBHub, the open-source MCP (Model Context Protocol) database server maintained by Bytebase, affecting the MySQL and MariaDB connectors in version 1.2.0 and earlier. The flaw lets a crafted SQL statement bypass DBHub’s "read-only mode" safety guarantee, allowing an attacker to write to, or drop tables from, a database the operator believed was exposed read-only. It carries a CVSS v3.1 base score of 9.1 (Critical).

Technical details

  • Root cause: DBHub’s SQL classifier (scanTokenMySQL in src/utils/sql-parser.ts) does not recognize # as a single-line comment delimiter for the MySQL/MariaDB dialect, even though MySQL and MariaDB servers do treat # as starting a comment.
  • Trigger conditions: An attacker submits a statement containing a #-prefixed region followed by a second, ;-separated statement. The classifier parses the # region as an ordinary string and sees only one harmless leading read statement, so it approves the request as read-only.
  • Execution path: DBHub’s MySQL/MariaDB connections are opened with multipleStatements enabled, and the original, unmodified SQL string (not the classifier’s sanitized view) is forwarded to the database driver. The database itself interprets # as a comment, so it sees and executes both statements — including the hidden write or DDL statement.
  • Attack vector: Network; no authentication is required in DBHub’s tested default configuration, since its HTTP transport is exposed unauthenticated. The payload can be delivered by any MCP client, or by an LLM agent driving one, that can reach the execute_sql tool configured with readonly = true.
  • Impact: Defeats the read-only enforcement operators rely on when exposing a database to an AI agent, enabling arbitrary writes and destructive DDL (e.g., DROP TABLE) or data modification against a MySQL or MariaDB backend.

Affected software

  • DBHub (@bytebase/dbhub, github.com/bytebase/dbhub) version 1.2.0 and earlier
  • Specifically impacts the MySQL and MariaDB connectors when the execute_sql tool is configured with readonly = true
  • Later releases had not been assessed for this issue as of the advisory’s publication

Severity

  • CVSS v3.1 Base Score: 9.1 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Mitigation and recommended actions

  • Immediate: No patched DBHub version had been published or confirmed at the time this advisory was disclosed. Monitor the bytebase/dbhub repository and upgrade as soon as a fix is released.
  • Workarounds (no patch available):
    • Disable multipleStatements on MySQL/MariaDB database connections used by DBHub, so stacked statements cannot execute regardless of the classifier’s decision.
    • Enforce read-only access at the database layer itself — via a read-only transaction or a least-privilege database account — rather than relying solely on DBHub’s client-side SQL classifier.
    • Restrict and authenticate network access to DBHub’s HTTP transport, since it is reachable without authentication by default.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge