CVE-2026-61742
Received Received - Intake

Unauthenticated HTTP MCP Endpoint in DBHub

Publication date: 2026-09-24

Last updated on: 2026-09-24

Assigner: GitHub, Inc.

Description
DBHub is a database MCP server for Postgres, MySQL, SQL Server, Oracle, MariaDB, SQLite. Versions prior to 0.22.5 expose an unauthenticated HTTP MCP endpoint when started with the documented HTTP transport mode, for example `--transport http --port 8080`. The HTTP server attempts to protect browser-origin access by checking whether the `Origin` hostname equals the `Host` hostname, then reflecting the validated `Origin` into `Access-Control-Allow-Origin`. This does not stop DNS rebinding. After an attacker-controlled hostname rebinds to a victim-accessible DBHub HTTP server, both `Origin` and `Host` can contain the attacker-controlled hostname, so DBHub accepts the request and dispatches MCP tool calls. As a result, a malicious website can deterministically invoke DBHub MCP tools from the victim's browser without prompt injection or model involvement. With the default demo configuration this can read and write the demo SQLite database; with a real configured database, the same primitive can read, enumerate, and potentially write database contents depending on DBHub's configured tool permissions and database credentials. Version 0.22.5 fixes the issue.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-09-24
Last Modified
2026-09-24
Generated
2026-09-24
AI Q&A
2026-09-24
EPSS Evaluated
N/A
NVD
CVE-2026-61742
EUVD
EUVD-2026-86320

Affected Vendors & Products

Currently, no data is known.

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-346 The product does not properly verify that the source of data or communication is valid.
CWE-306 The product does not perform any authentication for functionality that requires a provable user identity or consumes a significant amount of resources.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

DBHub versions before 0.22.5 have an unauthenticated HTTP MCP endpoint when using HTTP transport mode. The server checks if the Origin header matches the Host header to allow cross-origin requests, but this does not prevent DNS rebinding attacks. An attacker can exploit this to make the victim's browser send malicious requests to the DBHub server, executing MCP tools without user interaction.

Detection Guidance

To detect this vulnerability, check if DBHub is running with the HTTP transport mode (e.g., --transport http --port 8080) on any system. Verify if the version is prior to 0.22.5. Inspect network traffic for unauthenticated HTTP MCP endpoint access attempts or unusual DNS rebinding patterns.

Impact Analysis

If you run a vulnerable DBHub instance, a malicious website could access your database through your browser without your knowledge. This could allow reading, writing, or enumerating database contents depending on DBHub's configuration and permissions. The impact ranges from data theft to unauthorized modifications.

Compliance Impact

This vulnerability could lead to unauthorized access or disclosure of sensitive data, violating GDPR's data protection principles and HIPAA's security requirements for protected health information. Organizations may face compliance violations, legal penalties, and reputational damage if exploited.

Mitigation Strategies

Immediately upgrade DBHub to version 0.22.5 or later. Disable the HTTP transport mode if not required. Restrict network access to DBHub instances using firewalls. Monitor for suspicious activity related to DNS rebinding or unauthorized MCP tool invocations.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-61742. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart