Impact
The vulnerability in dbt-mcp results in the unredacted logging of every tool invocation, with the full argument dictionary—including raw SQL queries, variable values, credentials, and node selection—from operations such as show, run, build, test, and compile—being sent to dbt Labs telemetry by default. Because usage tracking is enabled out of the box and can only be suppressed by setting DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1, any execution of the MCP tool without explicit opt‑out will transmit sensitive data to the telemetry server. The flaw represents an unsecured data transmission weakness (CWE-201).
Affected Systems
All releases of dbt-labs dbt-mcp before version 1.17.1 are affected. This includes every minor and patch release of those versions up to and including 1.17.0.
Risk and Exploitability
The EPSS score is less than 1% illustrating a low probability that an attacker will actively exploit the vulnerability. However, the exposure does not require a traditional exploit: any user whose telemetry is enabled will automatically send the data. The CVSS score of 3.1 reflects a low severity, primarily due to the confidentiality impact. The vulnerability is not listed in CISA KEV, indicating no widespread exploitation was observed to date. Nevertheless, the risk of leaking proprietary SQL or credentials remains when telemetry is on, making it advisable to mitigate promptly.
OpenCVE Enrichment
Github GHSA