Vulnerability in dbt-mcp (CVE-2026-44970)
Summary
Vulnerability in dbt-mcp (CVE-2026-44970). Risk of unauthorized operations or information disclosure. Exploitable via arguments. 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, DefaultUsageTracker.emit_tool_called_event() in src/dbt_mcp/tracking/tracking.py serialized every MCP tool call's complete arguments dictionary and sent it through dbtlabs_vortex.producer.log_proto without redaction, including sql_query from show, vars from run, build, and test, and node_selection from compile, while usage_tracking_enabled in settings.py enabled telemetry by default unless DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 was set. 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-44970 has been found in dbt-mcp.
Attackers can target a specific entry point like arguments over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 3.1/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-44970" on the vendor's site.
CVE-2026-44970 (dbt-mcp) — CWE-201 / CVSS v3 3.1
Attack vector: remote (network-reachable) / no user interaction
Attack surface: arguments / dbtlabs_vortex.producer.log_proto / sql_query / show
Patched: 1.17.1 — apply immediately
Workaround: set usage_tracking_: 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.
A vulnerability (CWE-201) exists in dbt-mcp. Attackers reach the vulnerable code path via arguments.
Check the vendor advisory for the affected versions of dbt-mcp. Attack surface: arguments / dbtlabs_vortex.producer.log_proto / sql_query / show.
Severity: Low (CVSS 3.1/10). Risk of unauthorized operations or information disclosure.
Update to 1.17.1.
Workaround: set usage_tracking_: enabled
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 temporary workaround mitigate
set usage_tracking_: enabledパッチが適用されるまでの応急処置として、set usage_tracking_: enabled を実施。回避策の副作用 (機能低下) を確認した上で。
-
3Apply patch patch
Upgrade dbt-mcp to 1.17.1ステージング環境で 1.17.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
4Post-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