Vulnerability in github.com/googleapis/mcp-toolbox (CVE-2026-11719)
Summary
Vulnerability in github.com/googleapis/mcp-toolbox (CVE-2026-11719). Confidential information can be exposed externally. Mitigation: upgrade to 1.4.0 or later.
Original description
The description as published by the source.
An authenticated authorization bypass vulnerability exists in MCP Toolbox for Databases due to missing scope enforcement across older protocol handlers.
While the 2025-11-25 protocol version handler correctly enforces per-tool restrictions defined by scopesRequired, older supported protocol versions (2025-06-18, 2025-03-26, and 2024-11-05) omit this check. An authenticated client with low-privilege tokens (e.g., read) can bypass the intended per-tool scope restrictions and execute high-privilege tools (e.g., admin) simply by specifying an older protocol version in the MCP-Protocol-Version header, or by omitting the header entirely (which causes the server to default to the vulnerable 2024-11-05 handler).
Source: GitHub Security Advisories (Global) 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-11719 has been found in github.com/googleapis/mcp-toolbox.
Confidential information can be exposed externally. CVSS score: 8.1/10.
What to do: upgrade github.com/googleapis/mcp-toolbox to 1.4.0 or later.
If unsure, ask your IT team or search "github.com/googleapis/mcp-toolbox CVE-2026-11719" on the vendor's site.
CVE-2026-11719 (github.com/googleapis/mcp-toolbox) — CWE-862 / CVSS v3 8.1
Attack vector: remote (network-reachable) / no user interaction
Patched: 1.4.0 — apply immediately
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.
A vulnerability (CWE-862) exists in github.com/googleapis/mcp-toolbox.
Check the vendor advisory for the affected versions of github.com/googleapis/mcp-toolbox.
Severity: High (CVSS 8.1/10). Confidential information can be exposed externally.
Update to 1.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/googleapis/mcp-toolbox' . 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
-
1Identify exposure identify
grep -r 'github.com/googleapis/mcp-toolbox' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/googleapis/mcp-toolboxを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/googleapis/mcp-toolbox to 1.4.0ステージング環境で 1.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- advisory github.com
- advisory github.com
- package github.com
- patch github.com
- patch github.com