Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-49257 critical CVSS 10.0

Vulnerability in mcp-pinot-server (CVE-2026-49257)

Summary

Vulnerability in mcp-pinot-server (CVE-2026-49257). Successful exploitation can lead to full system takeover. Exploitable via Authorization header. Mitigation: upgrade to 3.1.0 or later.

Original description

The description as published by the source.

Resolution

Fixed in v3.1.0, released 2026-05-25. The fix was merged in PR #95 at commit 1c7d3f9.

The fix changes the default HTTP bind host to 127.0.0.1, refuses non-loopback HTTP/HTTPS exposure unless OAuth is enabled, makes Helm exposure opt-in and OAuth-gated, and adds parser-backed single-statement read-only validation for read-query.

CVSS evaluation

Reviewed on 2026-05-25. The advisory remains Critical with CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H = 10.0.

Rationale:

Metric Value Reason
AV Network The default HTTP server bound to 0.0.0.0:8080 and accepted remote HTTP requests.
AC Low Exploitation required only a direct MCP tool call.
PR None OAuth was disabled by default.
UI None No user interaction was required.
S Changed The vulnerable MCP server used its server-side credentials to act on the separate Pinot cluster security boundary.
C High Unauthenticated callers could read table data and cluster metadata through server-side Pinot credentials.
I High Unauthenticated callers could create or update schemas and table configs where the server-side account had those privileges.
A High Expensive queries and configuration mutations could degrade or disr…

Source: NIST National Vulnerability Database NVD GitHub Advisory

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-49257 has been found in mcp-pinot-server.
Attackers can target a specific entry point like Authorization header over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 10.0/10.
What to do: upgrade mcp-pinot-server to 3.1.0 or later.
If unsure, ask your IT team or search "mcp-pinot-server CVE-2026-49257" on the vendor's site.

CVE-2026-49257 (mcp-pinot-server) — CWE-306 / CVSS v3 10.0
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Attack surface: Authorization header / main / oauth_enabled / _auth
Patched: 3.1.0 — apply immediately
Workaround: set OAUTH_: ENABLED
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (CWE-306) exists in mcp-pinot-server. Attackers reach the vulnerable code path via Authorization header without authentication.

📍 Affected scope

Check the vendor advisory for the affected versions of mcp-pinot-server. Attack surface: Authorization header / main / oauth_enabled / _auth.

🔥 Severity

Severity: Critical (CVSS 10.0/10). Successful exploitation can lead to full system takeover.

🔧 How to fix

Update to 3.1.0.

🛡️ Workaround

Workaround: set OAUTH_: ENABLED

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'mcp-pinot-server' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

  1. 1
    Identify exposure identify 
    grep -r 'mcp-pinot-server' . | grep -v node_modules

    リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で mcp-pinot-server を grep し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply temporary workaround mitigate 
    set OAUTH_: ENABLED

    パッチが適用されるまでの応急処置として、set OAUTH_: ENABLED を実施。回避策の副作用 (機能低下) を確認した上で。

  3. 3
    Apply patch patch 
    Upgrade mcp-pinot-server to 3.1.0

    ステージング環境で 3.1.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  4. 4
    Post-deployment verification verify 
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

pip mcp-pinot-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]
PyPI mcp-pinot-server
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"3.1.0"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details