# 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.

- **Severity:** Low 3.1 (`CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 18 Jul 2026
- **Also known as:** GHSA-jj54-r8gm-2fcf, PYSEC-2026-2442

## 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 (Insertion of Sensitive Information Into Sent Data)

## Which versions are affected by CVE-2026-44970?

3 open source packages ship an affected version, including dbt-mcp. It affects 1 product.


| Package | Ecosystem | 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: 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

- [CVE-2026-44968](https://insights.sbomify.com/CVE-2026-44968/): dbt-mcp: Argument Injection in dbt CLI Tool Wrappers via node_selection and resource_type Parameters (medium 6.3)
- [CVE-2026-44969](https://insights.sbomify.com/CVE-2026-44969/): dbt MCP Server Logs Tool Arguments Including SQL Queries and Credentials in Plaintext Without Redaction When File Logging Is Enabled (low 2.5)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44970 and fix it if it is affected.

What it is: 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.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44970 exists.

Affected packages and fixed versions:
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44970/ (Markdown: https://insights.sbomify.com/CVE-2026-44970/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44970
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44970
- OSV: https://osv.dev/vulnerability/CVE-2026-44970

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44970/
Summaries are generated and may contain mistakes; the official description above is the record.