Advisory record · GHSA-73cv-556c-w3g6

mcp-pinot: Unauthenticated tool invocation via default oauth_enabled=False + host 0.0.0.0 bind

CVSS 10.0 CriticalCriticalEPSS 0.0062 · 50th percentile

Critical, because:

  • CVSS score 10.0: 9.0 or more.

How we decide what’s critical

Published by the GitHub Advisory Database at 26 Jun 2026, 21:05 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
mcp-pinot-serverPyPI<3.1.03.1.0
Identifiers
GHSA-73cv-556c-w3g6 · CVE-2026-49257 · PYSEC-2026-410
Weakness (CWE)
CWE-306
Published
26 Jun 2026
Updated
16 Nov 2026

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.

Written 6 Nov 2026.

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

ScoreRatingCVSSVectorSource
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

  1. 26 Jun 2026, 21:05 UTC Confirmed by GitHub Advisory Database
  2. 31 Oct 2026, 15:04 UTC First seen by agentprime
  3. 31 Oct 2026, 15:04 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.