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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS 4.0

6.1 · 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 · score source

EPSS

• CVE-2026-61789: 0.39% estimated exploitation activity in the next 30 days; percentile 32.60 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 cause The problem is a mismatch between how DBHub's SQL parser handles single-line comments and how MySQL and MariaDB actually parse them. In src/utils/sql-parser.ts, scanSingleLineComment treats "--" as the start of a comment no matter what character follows it. MySQL and MariaDB only begin a "--" comment when the two dashes are followed by whitespace, a control character, or the end of the line. Otherwise the dashes are read as two minus signs and the rest of the line is ordinary SQL. The read-only check in src/tools/execute-sql.ts splits the input and validates each statement with isReadOnlySQL, but the connector then executes the original, unmodified string. The MySQL and MariaDB connectors…

Published by the source

2 Nov 2026, 17:57 UTC

Last modified by the source

2 Nov 2026, 18:15 UTC

Source last checked

3 Nov 2026, 06:00 UTC

1. Revision 2 · amended · 3 Nov 2026

   Amended from osv record GHSA-j656-3hf2-fvjc

2. Revision 1 · created · 2 Nov 2026

   Published from ghsa record GHSA-j656-3hf2-fvjc

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-61789

Advisory: DBHub: MySQL and MariaDB comment interpretation bypasses read-only SQL validation
IDs: CVE-2026-61789, GHSA-j656-3hf2-fvjc
Record: https://patchnext.com/advisories/ghsa-j656-3hf2-fvjc (revision 2, source checked 3 Nov 2026, 06:00 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 6.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: @bytebase/dbhub 0.22.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- npm @bytebase/dbhub: affected < 0.22.6; fixed in 0.22.6

## Suggested inspection (read-only)
- `npm ls @bytebase/dbhub --all`: lists every installed copy and version, including transitive ones. Run in the project root after `npm ci`.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on @bytebase/dbhub.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://github.com/advisories/GHSA-j656-3hf2-fvjc (GitHub-reviewed advisory GHSA-j656-3hf2-fvjc lists affected ranges: npm @bytebase/dbhub >=0 <0.22.6)
- Verified: https://osv.dev/vulnerability/GHSA-j656-3hf2-fvjc (OSV record GHSA-j656-3hf2-fvjc lists affected ranges: npm @bytebase/dbhub >=0 <0.22.6 (fixed))

Commands are suggestions: review each one before running it.