DEV Community

CVE Reports
CVE Reports

Posted on Originally published at cvereports.com

CVE-2026-61788: CVE-2026-61788: Read-Only Bypass in DBHub Database Model Context Protocol Server

#security #cve #cybersecurity

CVE-2026-61788: Read-Only Bypass in DBHub Database Model Context Protocol Server

Vulnerability ID: CVE-2026-61788
CVSS Score: 7.4
Published: 2026-09-24

CVE-2026-61788 identifies a critical vulnerability in DBHub, an open-source database Model Context Protocol (MCP) server designed to manage and interact with database engines including PostgreSQL, MySQL, SQL Server, Oracle, MariaDB, and SQLite. Prior to version 0.22.6, DBHub fails to securely enforce its declared 'readonly' execution mode. Unauthenticated remote attackers can bypass keyword-based filters and transaction controls to execute arbitrary write operations, manipulate database sequences, read or write files on the host operating system, and potentially execute arbitrary system commands.

TL;DR

DBHub versions prior to 0.22.6 fail to enforce read-only execution constraints. Attackers can execute arbitrary SQL write operations, modify host files, and run commands by exploiting unauthenticated access to the default /mcp endpoint combined with parser-specific string bypasses.

⚠️ Exploit Status: POC

Technical Details

  • CWE ID: CWE-184 / CWE-636 / CWE-863
  • Attack Vector: Network (AV:N)
  • CVSS v3.1 Score: 7.4
  • Exploit Status: poc
  • CISA KEV Status: No
  • Affected Component: DBHub Connection Manager & Query Parser
  • Impact: Incorrect Authorization (Read-Only Policy Bypass)

Affected Systems

  • DBHub Model Context Protocol (MCP) Server
  • @bytebase/dbhub: < 0.22.6 (Fixed in: 0.22.6)

Code Analysis

Commit: 872bb33

Fix: secure read-only execution modes across PostgreSQL, SQLite, MySQL, and MariaDB connectors, and resolve comment parsing bypasses.

Mitigation Strategies

  • Upgrade DBHub to version 0.22.6 or higher to enable native transaction-level read-only locks.
  • Bind DBHub to localhost (127.0.0.1) instead of the wildcard address (0.0.0.0) to prevent external exposure.
  • Use host-based firewalls or network access control lists to restrict access to the /mcp endpoint.
  • Enforce the Principle of Least Privilege (PoLP) on the database accounts connected to DBHub.

Remediation Steps:

  1. Check the running version of @bytebase/dbhub in your npm or deployment environment.
  2. If the version is less than 0.22.6, execute an upgrade command, such as npm install @bytebase/dbhub@0.22.6.
  3. Locate the configuration file or startup script and ensure the server listening parameter is set to 127.0.0.1.
  4. Modify the user permissions of database engines managed by DBHub, revoking direct write access from credentials used for general analysis.

References

Read the full report for CVE-2026-61788 on our website for more details including interactive diagrams and full exploit analysis.

Top comments (0)