CVE-2026-49257

CRITICALPre-NVD 10.010.0—
EchelonGraph scoreMEDIUM confidence

This critical-severity CVE scores 10.0 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.5%, top 60% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).

Triggered by: NVD CVSS baseline
Sources: epss, secondary
10.0
EchelonGraph verdictPlan a fixSerious severity, but no confirmed exploitation yet.
  • High severity, but no confirmed exploitation yet
CISA-KEV: Not listedEPSS: 0%CVSS: 10.0Exploit: NoneExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

mcp-pinot is a Python-based Model Context Protocol (MCP) server for interacting with Apache Pinot. In versions 3.0.1 and below, mcp-pinot defaults to running an HTTP MCP server bound to 0.0.0.0:8080 with no authentication enabled. All MCP tools, including SQL query execution, schema creation, and table-config mutation, are reachable by any network-adjacent caller. The server proxies these calls using server-side Pinot credentials, producing a confused-deputy condition that yields full read/write access to the configured Pinot cluster. This issue has been fixed in version 3.1.0

CVSS v3
10.0
EG Score
10.0(medium)
EG Risk
50(Track)
EG Risk 50/100SSVC: Track

EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).

How it’s computed
Severity100% × 45%
Exploitation1% × 40%
Automatability30% × 15%
Action: Routine — remediate on your standard cadence.
EPSS
39.7%
KEV
Not listed

Published

June 18, 2026

Last Modified

June 23, 2026

Advisory Details (4)

Auto-updated Jul 22, 2026
Patch available. Sources: github_commit, github_pr, github.
github Patch Available

Unauthenticated tool invocation via default oauth_enabled=False + host 0.0.0.0 bind · Advisory · startreedata/mcp-pinot · GitHub

https://github.com/startreedata/mcp-pinot/security/advisories/GHSA-73cv-556c-w3g6
github_pr Patch Available

[codex] fix read-query exposure safeguards

Patch available: startreedata/mcp-pinot v3.1.0 (PR #95 merged 2026-05-25)

https://github.com/startreedata/mcp-pinot/pull/95
generic

SQL Injection vulnerability · Issue #90 · startreedata/mcp-pinot · GitHub

https://github.com/startreedata/mcp-pinot/issues/90
github_commit Patch Available

commit 1c7d3f9cd384 (startreedata/mcp-pinot)

Patch available: startreedata/mcp-pinot v3.1.0 (contains commit 1c7d3f9cd384)

https://github.com/startreedata/mcp-pinot/commit/1c7d3f9cd384854bf72c127d230bdb32299475ad

Vendor Advisories for CVE-2026-49257(1)

These vendors published their own advisory mentioning this CVE — often with vendor-specific remediation steps + affected product lists not in NVD.

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
mcp-pinot-server0.1.0 ... 3.0.1 (9 versions)3.1.0—

Weakness Classification(1)

MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.

Data Freshness Timeline

(refreshed 9× in last 7d / 33× in last 30d)

Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.

  1. 2026-07-23 14:18 UTCEPSS rescore
  2. 2026-07-23 03:18 UTCEG score recompute
  3. 2026-07-22 14:08 UTCEPSS rescore
  4. 2026-07-21 15:25 UTCEPSS rescore
  5. 2026-07-20 17:08 UTCEPSS rescore
  6. 2026-07-19 14:31 UTCEPSS rescore
  7. 2026-07-19 14:31 UTCEPSS rescore
  8. 2026-07-19 02:29 UTCEPSS rescore
  9. 2026-07-18 10:04 UTCEPSS rescore
  10. 2026-07-16 17:03 UTCEPSS rescore
  11. 2026-07-15 16:57 UTCEPSS rescore
  12. 2026-07-15 02:00 UTCEPSS rescore
  13. 2026-07-13 22:30 UTCEPSS rescore
  14. 2026-07-13 06:13 UTCEPSS rescore
  15. 2026-07-12 05:46 UTCEPSS rescore
  16. 2026-07-11 08:27 UTCEPSS rescore
  17. 2026-07-09 19:10 UTCEPSS rescore
  18. 2026-07-08 15:16 UTCEPSS rescore
  19. 2026-07-07 13:46 UTCEPSS rescore
  20. 2026-07-06 16:27 UTCEPSS rescore
  21. 2026-07-06 02:23 UTCEPSS rescore
  22. 2026-07-05 02:30 UTCEPSS rescore
  23. 2026-07-04 06:31 UTCEPSS rescore
  24. 2026-07-01 15:07 UTCEPSS rescore
  25. 2026-06-30 23:22 UTCEPSS rescore
Show 12 more
  1. 2026-06-29 14:06 UTCEPSS rescore
  2. 2026-06-29 14:06 UTCEPSS rescore
  3. 2026-06-28 14:07 UTCEPSS rescore
  4. 2026-06-28 04:56 UTCEPSS rescore
  5. 2026-06-28 04:56 UTCEPSS rescore
  6. 2026-06-27 03:08 UTCEPSS rescore
  7. 2026-06-25 13:49 UTCEPSS rescore
  8. 2026-06-24 14:05 UTCEPSS rescore
  9. 2026-06-23 21:33 UTCEPSS rescore
  10. 2026-06-23 21:33 UTCEPSS rescore
  11. 2026-06-18 21:24 UTCEG score recompute
  12. 2026-06-18 21:23 UTCNVD updatefirst tracked

Related CVEs(same CWE)

Frequently asked(5)

What is CVE-2026-49257?
CVE-2026-49257 is a critical vulnerability published on June 18, 2026. mcp-pinot is a Python-based Model Context Protocol (MCP) server for interacting with Apache Pinot. In versions 3.0.1 and below, mcp-pinot defaults to running an HTTP MCP server bound to 0.0.0.0:8080 with no authentication enabled. All MCP tools, including SQL query execution, schema creation, and…
When was CVE-2026-49257 disclosed?
CVE-2026-49257 was first published in the National Vulnerability Database on June 18, 2026, with the most recent update on June 23, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-49257 actively exploited?
CVE-2026-49257 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 39.7% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-49257?
CVE-2026-49257 has a CVSS v3 base score of 10.0 (NVD).
How do I remediate CVE-2026-49257?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-49257, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.

Dependency Blast Radius

See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-49257

Explore →

Is Your Infrastructure Affected by CVE-2026-49257?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs