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

New CVE Detected

CVE-2026-59971 – Unauthenticated Remote SQL Execution (RCE) – MySQL MCP Server < 0.4.2

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

Summary

CVE-2026-59971 is a critical missing-authentication / origin-validation vulnerability affecting the mysql_mcp_server package (designcomputer) when run in SSE/HTTP transport mode. Versions prior to 0.4.2 fail to enforce DNS-rebinding protection, CORS restrictions, or any authentication on the server’s /, /sse, and /messages/ endpoints, allowing a remote, unauthenticated attacker to execute arbitrary SQL queries against the backend MySQL database. The issue carries the maximum CVSS v3.1 score of 10.0 (Critical) due to full compromise of confidentiality, integrity, and availability with no privileges or user interaction required.

Technical details

  • Root cause: When started with SSE/HTTP transport, the server constructs the MCP SDK’s SseServerTransport without supplying security_settings, which leaves the SDK’s built-in DNS-rebinding protection (enable_dns_rebinding_protection) disabled by default. The underlying Starlette application also lacks CORS and TrustedHost middleware, and none of its routes require credentials.
  • Trigger conditions: The vulnerability only manifests when the server is launched with MCP_TRANSPORT=sse; the default stdio transport mode is not affected. The service also binds to 0.0.0.0 by default, exposing it on all network interfaces.
  • Attack vector: Network (AV:N), no privileges or user interaction required. An attacker can either (a) directly reach an exposed /sse or /messages/ endpoint over the network, or (b) use DNS rebinding to redirect a victim browser’s requests to a locally-bound instance, bypassing same-origin protections.
  • Impact: Once reachable, an attacker can invoke the server’s execute_sql tool to run arbitrary SQL commands without any credentials. This enables full database read/write access and, where the connected MySQL account holds FILE privileges, can be escalated to arbitrary file read/write and remote code execution on the host.

Affected software

  • mysql_mcp_server (designcomputer) — all versions prior to 0.4.2, when configured with MCP_TRANSPORT=sse

Severity

  • CVSS v3.1 Base Score: 10.0 (Critical)
  • Vector: CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Mitigation and recommended actions

  • Immediate: Upgrade mysql_mcp_server to version 0.4.2 or later, which enables DNS-rebinding protection (TransportSecuritySettings(enable_dns_rebinding_protection=True)) and no longer defaults to an unauthenticated, unrestricted binding.
  • If immediate patching is not possible:
    • Avoid running the server with MCP_TRANSPORT=sse until patched; use the default stdio transport where feasible.
    • Bind the service to 127.0.0.1 rather than 0.0.0.0 to prevent direct network exposure.
    • Place any SSE/HTTP-mode instance behind a reverse proxy or firewall that enforces authentication and restricts access to trusted hosts/origins only.
    • Restrict the MySQL account used by the server to the minimum required privileges, and explicitly revoke FILE privileges to reduce the risk of RCE via file operations.

References

Are you exposed?

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

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

Subscribe to Threat Center RSS

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

Get Real-Time CVE Alerts to Your Email

Be the first to know when new zero-days emerge