CVE-2026-44970: CWE-201: Insertion of Sensitive Information Into Sent Data in dbt-labs dbt-mcp
A vulnerability in dbt-labs dbt-mcp prior to version 1.17.1 allows sensitive information to be inserted into sent telemetry data. The DefaultUsageTracker.emit_tool_called_event() function serialized and transmitted complete tool call arguments, including potentially sensitive fields such as SQL queries and variables, without redaction. This telemetry is enabled by default unless explicitly disabled via environment variables. The issue is fixed in version 1.17.1.
AI Analysis
Technical Summary
In dbt-labs dbt-mcp versions before 1.17.1, the DefaultUsageTracker.emit_tool_called_event() method in tracking.py sends the full arguments dictionary of every MCP tool call through the telemetry system without redacting sensitive information. This includes sql_query from show commands, vars from run, build, and test commands, and node_selection from compile commands. Telemetry is enabled by default unless disabled by setting DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1. The vulnerability is classified as CWE-201 (Insertion of Sensitive Information Into Sent Data). The issue was resolved in version 1.17.1.
Potential Impact
Sensitive information such as SQL queries and variable values may be transmitted in telemetry data, potentially exposing confidential data to telemetry receivers. The CVSS score is low (3.1) reflecting limited impact and the requirement for network access with high attack complexity and low privileges. There is no indication of known exploits in the wild.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later where this issue is fixed. Alternatively, disable telemetry by setting the environment variables DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 to prevent sensitive data from being sent. No other mitigation is indicated.
CVE-2026-44970: CWE-201: Insertion of Sensitive Information Into Sent Data in dbt-labs dbt-mcp
Description
A vulnerability in dbt-labs dbt-mcp prior to version 1.17.1 allows sensitive information to be inserted into sent telemetry data. The DefaultUsageTracker.emit_tool_called_event() function serialized and transmitted complete tool call arguments, including potentially sensitive fields such as SQL queries and variables, without redaction. This telemetry is enabled by default unless explicitly disabled via environment variables. The 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
In dbt-labs dbt-mcp versions before 1.17.1, the DefaultUsageTracker.emit_tool_called_event() method in tracking.py sends the full arguments dictionary of every MCP tool call through the telemetry system without redacting sensitive information. This includes sql_query from show commands, vars from run, build, and test commands, and node_selection from compile commands. Telemetry is enabled by default unless disabled by setting DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1. The vulnerability is classified as CWE-201 (Insertion of Sensitive Information Into Sent Data). The issue was resolved in version 1.17.1.
Potential Impact
Sensitive information such as SQL queries and variable values may be transmitted in telemetry data, potentially exposing confidential data to telemetry receivers. The CVSS score is low (3.1) reflecting limited impact and the requirement for network access with high attack complexity and low privileges. There is no indication of known exploits in the wild.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later where this issue is fixed. Alternatively, disable telemetry by setting the environment variables DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 to prevent sensitive data from being sent. No other mitigation is indicated.
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/16/2026, 18:17:31 UTC
Last updated: 07/17/2026, 02:25:21 UTC
Views: 13
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.