CVE-2026-44970: CWE-201: Insertion of Sensitive Information Into Sent Data in dbt-labs dbt-mcp
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.
AI Analysis
Technical Summary
The vulnerability in dbt-mcp (CVE-2026-44970) involves the insertion of sensitive information into telemetry data sent by the DefaultUsageTracker.emit_tool_called_event() function. Before version 1.17.1, this function serialized the entire arguments dictionary of each MCP tool call and transmitted it without redacting sensitive fields such as sql_query, vars, and node_selection. Usage tracking is enabled by default unless explicitly disabled via environment variables. This could lead to unintended exposure of sensitive data through telemetry. The issue is fixed in version 1.17.1.
Potential Impact
Sensitive information including SQL queries and variables may be transmitted in telemetry data without redaction, potentially exposing confidential data. The impact is limited to confidentiality (low severity) with no integrity or availability effects. Exploitation requires network access to intercept telemetry data or access to the telemetry receiver. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later, where this issue is fixed. Alternatively, disable usage tracking by setting the environment variables DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 to prevent telemetry data from being sent. Patch status is not explicitly stated but the fix is included in version 1.17.1.
CVE-2026-44970: CWE-201: Insertion of Sensitive Information Into Sent Data in dbt-labs dbt-mcp
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.
CVSS v3.1
Score 3.1low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability in dbt-mcp (CVE-2026-44970) involves the insertion of sensitive information into telemetry data sent by the DefaultUsageTracker.emit_tool_called_event() function. Before version 1.17.1, this function serialized the entire arguments dictionary of each MCP tool call and transmitted it without redacting sensitive fields such as sql_query, vars, and node_selection. Usage tracking is enabled by default unless explicitly disabled via environment variables. This could lead to unintended exposure of sensitive data through telemetry. The issue is fixed in version 1.17.1.
Potential Impact
Sensitive information including SQL queries and variables may be transmitted in telemetry data without redaction, potentially exposing confidential data. The impact is limited to confidentiality (low severity) with no integrity or availability effects. Exploitation requires network access to intercept telemetry data or access to the telemetry receiver. No known exploits are reported in the wild.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later, where this issue is fixed. Alternatively, disable usage tracking by setting the environment variables DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 to prevent telemetry data from being sent. Patch status is not explicitly stated but the fix is included in version 1.17.1.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T16:23:33.263Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a591cd868715ace4377b004
Added to database: 07/16/2026, 18:03:04 UTC
Last enriched: 07/23/2026, 22:38:33 UTC
Last updated: 08/30/2026, 10:52:09 UTC
Views: 90
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.