cve.bz

CVE-2026-61788 bytebase dbhub: Incomplete List of Disallowed Inputs

7.4 highEPSS 0.4%Fix available

High (7.4) in bytebase dbhub. EPSS 0.4% estimated probability of exploitation activity in the next 30 days. Fixed in @bytebase/dbhub 0.22.6.

On this page
DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite. Prior to version 0.22.6, setting `readonly = true` on the `execute_sql` tool does not make the connection read-only. The connectors are written to set PostgreSQL `default_transaction_read_only=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 thing left enforcing read-only is a classifier that inspects the first keyword of each statement. Any `SELECT` that writes or has side effects through a function call passes it. With an ordinary role this allows sequence tampering; with a privileged role it allows writing arbitrary files on the server (`lo_export`), reading arbitrary host files (`pg_read_file`), and remote code execution (`dblink` + `COPY ... TO PROGRAM`). The HTTP transport is unauthenticated and binds to `0.0.0.0` by default, so this is reachable by any network caller of `/mcp`. Version 0.22.6 patches the issue.

Severity

CVSS 3.1

7.4 high
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
EPSS
0.4% (unchanged from 0.4% a week ago; 0.3% 30 days ago) estimated probability of exploitation activity in the next 30 days; 35th percentile. Scored 2026-11-17. A forecast for this CVE across the internet, not for your own systems.
CISA's assessment (SSVC)
Exploitation: PoC · Automatable: no · Technical impact: total, assessed 2026-09-29. From CISA's Vulnrichment in the CVE List: whether it is exploited, whether exploiting it can be automated, and how much control it gives.
CWEs
CWE-184 Incomplete List of Disallowed Inputs
CWE-636 Not Failing Securely (Failing Open)
CWE-863 Incorrect Authorization
OWASP Top 10
A01:2025 Broken Access Control, A10:2025 Mishandling of Exceptional Conditions
Published
Modified
NVD analysis
Deferred: the NVD does not plan to analyze it
Record from
the NVD, synced

Fix and patched versions

  • @bytebase/dbhub (npm): fixed in 0.22.6

Ask an AI about this CVE

Show the promptExplain CVE-2026-61788 for an engineer deciding whether to act. Use https://cve.bz/api/public/cves/CVE-2026-61788?via=ask-ai-copy and https://cve.bz/cve/CVE-2026-61788?via=ask-ai-copy as the source of truth: what is affected and which versions fix it, whether it is in CISA KEV, public exploits, and its EPSS (an internet-wide 30-day estimate of exploitation activity, not a forecast for my systems). If they give no fixed versions, use the CVE record https://cveawg.mitre.org/api/cve/CVE-2026-61788 or the vendor advisory, not third-party mirrors. Tell me how to check whether I am affected and how to verify a fix. Cite the sources and say where they are uncertain.

Opens a third-party assistant; its answer is its own, not cve.bz's. The prompt holds only this CVE's id and public links.

Affected

Versions

From the CNA's record in the CVE List.

ProductAffected
bytebase dbhub< 0.22.6

Packages (OSV)

AdvisoryEcosystemPackageAffectedFixed in
GHSA-mwwr-p57h-56pfnpm@bytebase/dbhub<0.22.60.22.6

Attack patterns (CAPEC)

  • CAPEC-3 Using Leading 'Ghost' Character Sequences to Bypass Input Filters Likelihood: Medium · Severity: Medium
  • CAPEC-6 Argument Injection Likelihood: High · Severity: High
  • CAPEC-15 Command Delimiters Likelihood: High · Severity: High
  • CAPEC-43 Exploiting Multiple Input Interpretation Layers Likelihood: Medium · Severity: High
  • CAPEC-71 Using Unicode Encoding to Bypass Validation Logic Likelihood: Medium · Severity: High
  • CAPEC-73 User-Controlled Filename Likelihood: High · Severity: High
  • CAPEC-85 AJAX Footprinting Likelihood: High · Severity: Low
  • CAPEC-120 Double Encoding Likelihood: Low · Severity: Medium
  • CAPEC-182 Flash Injection Likelihood: High · Severity: Medium

The attack patterns MITRE's CAPEC relates to this record's weaknesses, as MITRE names them. Credits.

References

Check your stackJSON