Machine-written summary
Summary written by Claude Haiku from the source advisory. Not reviewed by a person.
The mcp-pinot-server PyPI package... wait, the instruction says don't name the ecosystem unless confusion is likely; here the package is mcp-pinot-server, affected before 3.1.0. The advisory says the default HTTP MCP server binds to all interfaces with authentication off, so a network-reachable caller can invoke all tools, including SQL reads and schema or table-config writes, using the server's Pinot credentials. Upgrade to version 3.1.0, which changes the default bind to 127.0.0.1 and requires OAuth for non-loopback HTTP exposure.
Not analysed yet
We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.
Severity and exploitation
| Score | Rating | CVSS | Vector | Source |
|---|---|---|---|---|
| 10.0 | Critical | 3.1 | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | CNA (GitHub_M) |
- CISA KEV Not listed.
- EPSS 0.0062, the 50th percentile, on 17 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.
Timeline
- 26 Jun 2026, 21:05 UTC Confirmed by GitHub Advisory Database
- 31 Oct 2026, 15:04 UTC First seen by agentprime
- 31 Oct 2026, 15:04 UTC Confirmed by OSV
Sources
- GitHub Advisory Database: GHSA-73cv-556c-w3g6
- OSV: GHSA-73cv-556c-w3g6
- github.com/startreedata/mcp-pinot/security/advisories/GHSA-73cv-556c-w3g6
- nvd.nist.gov/vuln/detail/CVE-2026-49257
- github.com/startreedata/mcp-pinot/issues/90
- github.com/startreedata/mcp-pinot/pull/95
- github.com/startreedata/mcp-pinot/commit/1c7d3f9cd384854bf72c127d230bdb32299475ad
- github.com/pypa/advisory-database/tree/main/vulns/mcp-pinot-server/PYSEC-2026-410.yaml
- github.com/startreedata/mcp-pinot
- pypi.org/project/mcp-pinot-server