Live Exposure Defense: From CVE to Confirmed Exposure in 12 Hours – See more

Back
New CVE Detected

CVE-2026-61742 – Authentication Bypass / DNS Rebinding SQL Execution – DBHub < 0.22.5

Be the first to know when new zero-days emerge:

Subscribe to Email Alerts
Subscribe to RSS Feed

Summary

CVE-2026-61742 is a critical vulnerability in DBHub, a database MCP (Model Context Protocol) server from Bytebase that exposes Postgres, MySQL, SQL Server, Oracle, MariaDB, and SQLite databases to AI tooling. When run in HTTP transport mode, DBHub’s origin-validation logic can be bypassed via DNS rebinding, allowing a malicious website to trigger unauthenticated SQL execution against a victim’s DBHub instance directly from the victim’s browser. The flaw is tracked as CWE-306 (Missing Authentication for Critical Function) and CWE-346 (Origin Validation Error), with a CVSS score of 9.3.

Technical details

  • Root cause: DBHub’s HTTP transport validates browser requests by checking that the Origin header’s hostname matches the Host header’s hostname; if they match, the request is treated as trusted and the origin is reflected back via Access-Control-Allow-Origin.
  • Trigger conditions: An attacker registers a domain that first resolves to a server hosting malicious JavaScript, lures a victim to visit it, then rebinds the DNS record for that domain to the victim’s locally/network-accessible DBHub HTTP endpoint. Once rebound, both Origin and Host contain the attacker’s hostname, satisfying DBHub’s check.
  • Attack vector: Network — no prior authentication, network access, prompt injection, or AI model involvement is required; the victim only needs to browse to the attacker’s page while DBHub’s HTTP transport (e.g., started with --transport http --port 8080) is reachable.
  • Impact: The attacker’s page can silently enumerate available MCP tools and dispatch database operations through the victim’s browser, allowing reading and enumeration of database contents and, depending on DBHub’s configured tool permissions and database credentials, writing to or modifying the database. In the default demo configuration, this exposes the bundled demo SQLite database; in production deployments, it exposes whatever database DBHub is configured to proxy.

Affected software

  • Bytebase DBHub (npm package @bytebase/dbhub), versions ≤ 0.22.4, when run with HTTP transport mode enabled.

Severity

  • CVSS score: 9.3 (Critical)
  • CVSS v4.0 vector: CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N

Mitigation and recommended actions

  • Immediate: Upgrade DBHub to version 0.22.5 or later, which fixes the origin-validation bypass.
  • If immediate patching is not possible:
    • Bind DBHub’s HTTP transport to loopback (127.0.0.1) rather than exposing it on network-accessible interfaces.
    • Avoid running DBHub’s HTTP transport mode in environments reachable by untrusted browsers until patched.
    • Restrict network access to the DBHub HTTP endpoint via firewall rules, and monitor for unexpected inbound requests with mismatched or unusual Origin/Host header pairs.

References

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report

How IONIX’s External Exposure Management Platform Detects and Validates
Zero-Days to Shrink MTTR

1

Map your entire attack surface (continously)

IONIX uses multi-factor discovery methods, including DNS analysis, certificate mapping, metadata inspection, and more, to automatically map every internet-facing asset across your environment. This includes cloud instances, third-party platforms, shadow IT, and even forgotten infrastructure that traditional tools miss.

2

Monitor for new CVEs

Dozens of threat intel feeds using agentic technology are continuously analyzed to detect the appearance of proof-of-concept code, exploit kits, and indicators of active targeting. IONIX goes further by applying AI to proactively evaluate whether emerging vulnerabilities are likely to be exploited, even before PoCs go public.

3

Identify Potential External Exposures

Not all CVEs matter. IONIX filters vulnerabilities by asking attacker-centric questions: Can it be reached from the internet? Does it require authentication? Is it being exploited in the wild? This dramatically reduces noise and focuses teams on threats that can actually be weaponized.

4

Create Safe, Scalable Exploit Validations

IONIX transforms real-world PoCs into safe, non-intrusive test payloads that can be run in production environments without disruption. These simulations are precisely targeted to the systems that are vulnerable, ensuring rapid validation without unnecessary load.

5

Execute Exploit Validations

By combining context about software stack, versioning, exposure status, and reachability, IONIX ensures that only the right payloads are executed against the right assets, maximizing efficiency and minimizing risk.

6

Drive Fast and Actionable Remediation

Results are routed through integrations with ticketing, SOAR, and SIEM tools. Issues are written in plain language, bundled into remediation clusters, and prioritized based on asset criticality, exploitability, and blast radius. This shortens mean time to remediation (MTTR) and empowers teams to act with confidence.

Are you exposed?

Get a free report of your organization’s exposure to this CVE and threat

  • Mapping of all Assets with this Technology
  • Identification of potentially exposed assets to this CVE
  • Confirmation of verified exploitable assets
Get Exposure Report
Close

Subscribe to Threat Center RSS

Copy/paste the link below into your preferred RSS reader or follow these instructions to subscribe to Slack alerts.

Open RSS feedSlack setup instructions

Close

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge