CVE-2026-61788
HIGHDescription
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.
How to fix
TridentStack Control can deploy fixes like this automatically across your Windows, macOS, and Linux fleet. See how it works
Remediation is compiled from vendor and distribution security advisories. Always confirm against the linked source for your exact version and platform.
CVSS v3 Vector
Exploitability
Impact
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N
Exploit Intelligence
Low risk: more likely to be exploited than 21% of all known CVEs.
References
Related Vulnerabilities
Other CWE-184 vulnerabilities, ordered by exploit likelihood. View all
| CVE | Severity | CVSS | EPSS | Exploited | Fix |
|---|---|---|---|---|---|
| CVE-2024-5217 | Critical | 9.8 | 100% | KEV | - |
| CVE-2022-43396 | High | 8.8 | 55% | - | Fix |
| CVE-2017-7525 | Critical | 9.8 | 38% | - | Fix |
| CVE-2024-5178 | Medium | 4.9 | 34% | - | - |
| CVE-2018-7489 | Critical | 9.8 | 20% | - | Fix |
| CVE-2018-6383 | High | 8.8 | 13% | - | - |
Common questions
How do I fix CVE-2026-61788?
Upgrade @bytebase/dbhub to 0.22.6 or later.
Is CVE-2026-61788 being actively exploited?
Not that we know of. CVE-2026-61788 is not in the CISA Known Exploited Vulnerabilities catalog. Its EPSS score of 0.30% is the estimated probability that it will be exploited in the next 30 days. That is higher than 21% of all scored CVEs.
How severe is CVE-2026-61788?
CVE-2026-61788 has a CVSS v3 base score of 7.4, rated high. CVSS rates the technical impact if the vulnerability is exploited, not how likely that is, so weigh it alongside the exploit-prediction score when you decide what to patch first.
What does CVE-2026-61788 affect?
Published advisories record a fix for @bytebase/dbhub (npm). Only products with a sourced advisory are listed, so treat this as what we can cite rather than a complete inventory.
Embed a live status badge for CVE-2026-61788
Markdown
[](https://tridentstack.com/cve/CVE-2026-61788)HTML
<a href="https://tridentstack.com/cve/CVE-2026-61788"><img src="https://tridentstack.com/cve/badge/CVE-2026-61788.svg" alt="CVE-2026-61788"></a>Find and fix vulnerabilities across your fleet
TridentStack Control continuously scans your Windows, macOS, and Linux fleet for known vulnerabilities, prioritizes them by severity and active exploitation, and patches them automatically.
This product uses NVD data but is not endorsed or certified by the NVD. EPSS scores courtesy of FIRST.org (https://www.first.org/epss). Source: CISA KEV Catalog. Data as of 2026-09-30.