AdvisoriesToolsStatsChecklistSubmitGet the email
← All advisories
CVE-2026-61742criticalBroken access control2026-06-24

CVE-2026-61742: DBHub MCP server's HTTP mode let any website query your database

DBHub, Bytebase's database MCP server, had no authentication in its HTTP transport mode before 0.22.5, and its Origin check didn't stop DNS rebinding. A malicious web page could make your browser call DBHub's MCP tools and read or write the connected database.

01.

What it is

Started with --transport http, DBHub only rejected requests whose Origin hostname differed from the Host hostname, then reflected the Origin back with credentials allowed.

After DNS rebinding, both headers carry the attacker's hostname, so the check passes and DBHub runs the MCP tool calls. No prompt injection or model is involved.

What an attacker can do depends on the configured database credentials and tool permissions: reading and listing data at minimum, and possibly writing. The default stdio transport isn't affected by this attack.

02.

How to check

  1. Affected: @bytebase/dbhub (npm) 0.22.4 and earlier, when run with --transport http.
  2. Check your MCP client config and any scripts for dbhub started with --transport http.
03.

How to fix

  1. Upgrade to @bytebase/dbhub 0.22.5 or later.
  2. Prefer the stdio transport, and give DBHub a read-only database user where you can.
npm ls @bytebase/dbhub; npm ls -g @bytebase/dbhub
04.

Sources

More advisories for this tool
The weekly email

One email a week. Only what changed.

Every new security hole in AI coding tools, MCP servers, app builders and the stacks they generate (Next.js, Supabase, Node, PHP), each with how to check your app and the fix. No roundups of things you already read.

Free, one email a week. Read the latest issue first if you like. One-click unsubscribe in every email. We never sell or share addresses.