CVE-2026-49257: mcp-pinot · Unauthenticated tool invocation via default oauth_enabled=False + host 0.0.0.0 bind
Affects mcp-pinot-serverSource GCVE Database
Not known to be exploited · CVSS 10.0 Critical : upgrade to 3.1.0 as a priority.
Data as of 16 Nov 2026, 16:50 UTC
- Patch
- Available – fixed in 3.1.0
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:HExploitation evidence
Disclosed: evidence found.
CVE published 18 Jun 2026
Detectable: no evidence on record.
No public nuclei template indexed
Weaponized: no evidence on record.
No public exploit code indexed in Metasploit or Exploit-DB
Exploited in the wildExploited: no evidence on record.
Not in CISA KEV and no source reports exploitation
Observed by OffSeq MirageSeen by Mirage: no evidence on record.
No attack traffic recorded by OffSeq Mirage sensors
A missing step is not evidence of safety. Sources: cve.org (opens in a new tab), the Metasploit, Exploit-DB and nuclei-templates index as of 15 Nov 2026.
What to do
Upgrade mcp-pinot-server to 3.1.0.
Affected software
| Product | Affected | Fixed in |
|---|---|---|
| PyPImcp-pinot-server | Affected
| Fixed in
|
Check your own hosts for these packages with threat-finder (opens in a new tab), our free open-source scanner.
AI-suggested
A fix is available in mcp-pinot version 3.1.0. Users should upgrade to this version or later. The fix changes the default HTTP bind host to 127.0.0.1, disables unauthenticated network exposure by requiring OAuth authentication for non-loopback interfaces, and makes Helm exposure opt-in and OAuth-gated. Operators should ensure OAuth is enabled and the server is not bound to 0.0.0.0 without authentication.
Description
mcp-pinot versions prior to 3.1.0 default to running an unauthenticated HTTP server bound to all network interfaces, allowing any network-adjacent attacker to invoke all MCP tools. This includes executing arbitrary SQL queries, reading cluster metadata, and modifying schemas and table configurations. The server uses privileged server-side Pinot credentials to proxy these requests, resulting in a confused-deputy vulnerability with full read/write access to the Pinot cluster. The issue is fixed in version 3.1.0 by changing the default bind host to localhost, requiring OAuth authentication for network exposure, and making Helm exposure opt-in and OAuth-gated.
References
- github.com/startreedata/mcp-pinot/security/advisories/GHSA-73cv-556c-w3g6 (opens in a new tab)
- nvd.nist.gov/vuln/detail/CVE-2026-49257 (opens in a new tab)
- github.com/startreedata/mcp-pinot/issues/90 (opens in a new tab)
- github.com/startreedata/mcp-pinot/pull/95 (opens in a new tab)
- github.com/startreedata/mcp-pinot/commit/1c7d3f9cd384854bf72c127d230bdb32299475ad (opens in a new tab)
- github.com/pypa/advisory-database/tree/main/vulns/mcp-pinot-server/PYSEC-2026-410.yaml (opens in a new tab)
- github.com/startreedata/mcp-pinot (opens in a new tab)
- pypi.org/project/mcp-pinot-server (opens in a new tab)