DBHub DNS rebinding and read-only bypass vulnerabilities

DBHub versions prior to 0.22.5 expose multiple critical vulnerabilities: an unauthenticated HTTP MCP endpoint vulnerable to DNS rebinding attacks allowing unauthorized database access, and a non-functional read-only mode that fails to prevent database writes including potential remote code execution.

Disclosed 24 September 2026 · Record updated 1 October 2026

Impact

Attackers can invoke DBHub MCP tools from victim browsers via DNS rebinding without authentication, potentially reading, enumerating, and writing database contents. Additionally, the read-only mode fails to enforce restrictions, allowing writes and potential RCE through SQL functions on PostgreSQL databases.

Our coverage

A locked vault door swings open as invisible hands redirect a compass needle, then a guard in read-only robes helplessly watches documents being written and removed.

Vulnerabilities

Two flaws in Bytebase's DBHub database MCP server disclosed

Advisories published on 24 September 2026 describe a DNS rebinding bypass and a read-only mode that never actually blocks writes.

24 Sept 2026

Sources

nvd.nist.govhttps://nvd.nist.gov/vuln/detail/CVE-2026-61742
github.comhttps://github.com/advisories/GHSA-fm8p-53ww-hf6w
github.comhttps://github.com/advisories/GHSA-mwwr-p57h-56pf