Skip to content
DayZeroHub
Critical CVSS 10GHSA-73cv-556c-w3g6CVE-2026-49257

mcp-pinot-server: Unauthenticated tool invocation due to default configuration

mcp-pinot-server

Summary

mcp-pinot-server versions up to 3.0.1 run, by default, an HTTP MCP server exposed on all interfaces with no authentication. Version 3.1.0 fixes the issue; the CVSS 3.1 score is 10.0 (critical).

What happened

According to the source, mcp-pinot version 3.0.1 and earlier starts by default an HTTP MCP server bound to 0.0.0.0:8080 with OAuth disabled. As a result, any caller with network access can invoke all of the server's tools, including SQL query execution, schema creation and table-config modification. The server makes those calls using the Pinot credentials configured on the server itself, which the source describes as a confused-deputy condition that grants read and write access to the configured Pinot cluster. The source states that all versions confirmed from v2.1.0 through v3.0.1 are affected, and classifies the issue as CWE-306 (missing authentication for a critical function). Identifiers: CVE-2026-49257 and GHSA-73cv-556c-w3g6.

Why it matters

The source rates the vulnerability CVSS 3.1 10.0 (critical), vector CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H: it is exploitable over the network, with no privileges or user interaction, and has high impact on confidentiality, integrity and availability. According to the vendor, table data and cluster metadata could be read, schemas and table configs could be created or updated (where the server-side account had those privileges), and Pinot availability could be degraded through expensive queries or configuration changes. The source does not indicate active exploitation (it is not listed in CISA's KEV catalog).

Affected products and versions

mcp-pinot-server (PyPI package, product mcp-pinot-server): versions <= 3.0.1. Fixed in 3.1.0. Files named: mcp_pinot/server.py and mcp_pinot/config.py.

ProductVersionsFixed in
mcp-pinot-server<= 3.0.13.1.0

Action recommended by the source

The vendor states the issue is fixed in v3.1.0. According to the source, the fix changes the default HTTP bind host to 127.0.0.1, refuses non-loopback HTTP/HTTPS exposure unless OAuth is enabled, makes Helm exposure opt-in and OAuth-gated, and adds single-statement read-only validation for read-query. The fix was merged in PR #95 (commit 1c7d3f9).

Fixed in: 3.1.0

Information taken from the source or the vendor. Verify it at the original link before acting.

Sources and references

Weaknesses (CWE): CWE-306

Relevant change history

  1. Published

    Advisory published.

Summary written with AI assistance from the source data. See the sources and references for complete information. View sources