Vulnerability in dbt-mcp (CVE-2026-44969)
Summary
Vulnerability in dbt-mcp (CVE-2026-44969). 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, DbtMCP.call_tool() in src/dbt_mcp/mcp/server.py logged the raw arguments dictionary at INFO level before each tool call and at ERROR level on exceptions, and configure_file_logging() wrote those records to dbt-mcp.log when DBT_MCP_SERVER_FILE_LOGGING=true, preserving sensitive sql_query, vars, and node_selection values in plaintext without automatic rotation or deletion. 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-44969 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: 2.5/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-44969" on the vendor's site.
CVE-2026-44969 (dbt-mcp) — CWE-532 / CVSS v3 2.5
Attack vector: local / no user interaction
Attack surface: arguments / INFO / ERROR / server.py
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-532) 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 / INFO / ERROR / server.py.
Severity: Low (CVSS 2.5/10). Risk of unauthorized operations or information disclosure.
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