Vulnerability in dbt-mcp (CVE-2026-44968)
Summary
Vulnerability in dbt-mcp (CVE-2026-44968). Confidential information can be exposed externally. Exploitable via node_selection. Mitigation: upgrade to 1.17.1 or later.
Original description
The description as published by the source.
dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, _run_dbt_command() in src/dbt_mcp/dbt_cli/tools.py appended unsanitized node_selection and resource_type values to the dbt subprocess argument list, allowing an MCP client to inject dbt global flags such as --profiles-dir, --project-dir, and --target into subprocess.Popen even though shell=False prevents shell metacharacter injection. This issue is fixed in version 1.17.1.
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-44968 has been found in dbt-mcp.
Attackers can target a specific entry point like node_selection over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: 6.3/10.
What to do: upgrade dbt-mcp to 1.17.1 or later.
If unsure, ask your IT team or search "dbt-mcp CVE-2026-44968" on the vendor's site.
CVE-2026-44968 (dbt-mcp) — CWE-88 / CVSS v3 6.3
Attack vector: local / no user interaction
Attack surface: node_selection / resource_type / subprocess.Popen / build
Patched: 1.17.1 — 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-88) exists in dbt-mcp. Attackers reach the vulnerable code path via node_selection.
Check the vendor advisory for the affected versions of dbt-mcp. Attack surface: node_selection / resource_type / subprocess.Popen / build.
Severity: Medium (CVSS 6.3/10). Confidential information can be exposed externally.
Update to 1.17.1.
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 'dbt-mcp' . 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 'dbt-mcp' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
dbt-mcpを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade dbt-mcp to 1.17.1ステージング環境で 1.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- advisory github.com
- advisory github.com
- advisory nvd.nist.gov
- package github.com
- patch github.com
- patch github.com
- web github.com
- web github.com