Unauthenticated MCP HTTP API grants full read/write access to Pinot clusters, affecting mcp-pinot <=3.0.1; potential disruption across analytics deployments.
CVE-2026-49257
Unauthenticated MCP HTTP API exposes full Pinot cluster access.
Is CVE-2026-49257 being exploited?
Not confirmed. CVE-2026-49257 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.93% probability of exploitation in the next 30 days.
How severe is CVE-2026-49257?
CVE-2026-49257 is rated Critical with a CVSS score of 10.0. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-49257?
Yes. A fix has been recorded for CVE-2026-49257. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-49257 affect?
CVE-2026-49257 affects mcp-pinot <= 3.0.1, Apache Pinot, MCP server. Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-49257?
Upgrade to 3.1.0+, enable auth, and restrict HTTP exposure.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Remote attacker can perform SQL, schema, and config mutations via MCP, gaining full Pinot cluster access.
Immediate action required
- affected< 3.1.0
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.