CVE-2026-44970 dbt MCP Server Transmits All MCP Tool Arguments Including Raw SQL and --vars Credentials to dbt Labs Telemetry by Default Without Redaction
Attackers with telemetry access can view sensitive SQL queries and credentials sent by dbt-mcp tools due to lack of redaction in default telemetry settings.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-44970?
CVE-2026-44970 is a low-severity vulnerability in dbt-labs dbt-mcp, published on 16 Jul 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
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.
Weakness: CWE-201
Which versions are affected by CVE-2026-44970?
3 open source packages ship an affected version, including dbt-mcp. It affects 1 product.
| Package | Affected | Fixed in |
|---|---|---|
dbt-mcp PyPI | All versions | 1.17.1 |
dbt-mcp PyPI | All versions | 1.17.1 |
dbt-mcp PyPI | All versions | 1.17.1 |
Products include Getdbt Dbt Mcp Server.
How do I fix CVE-2026-44970?
Upgrade dbt-mcp to 1.17.1 or later.
Is CVE-2026-44970 being exploited?
It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44970 exists.
Other vulnerabilities in dbt-labs dbt-mcp
Sources
Also known as GHSA-jj54-r8gm-2fcf, PYSEC-2026-2442.