Quick answers
- Is CVE-2026-44970 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44970 being exploited in the wild.
- How severe is CVE-2026-44970?
- Low severity, with a CVSS score of 3.1, published 16 July 2026.
- Which products and versions are affected?
- dbt-mcp (PyPI) <= 1.17.0, ECOSYSTEM:introduced=0,fixed=1.17.1.
- Is there a fix for CVE-2026-44970?
- Yes. dbt-mcp (PyPI): upgrade to 1.17.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44970 attacked?
- It is attacked over the network, in a software library.
- Am I affected by CVE-2026-44970?
- Check whether you run dbt-mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- dbt-mcp (PyPI): upgrade to 1.17.1 or later
pip install "dbt-mcp>=1.17.1"
Technical details
The vulnerability exists in the `DefaultUsageTracker.emit_tool_called_event()` function within `src/dbt_mcp/tracking/tracking.py`. The component serializes the complete arguments dictionary of every MCP tool call and transmits it to the dbt Labs telemetry service via `dbtlabs_vortex.producer.log_proto` without redaction. This includes sensitive fields such as `sql_query` from the 'show' tool and `vars` (which often contain credentials) from 'run', 'build', and 'test' tools. Telemetry is enabled by default unless specifically opted out via environment variables. An attacker with low privileges who can trigger tool calls could cause the leakage of sensitive configuration or query data to the telemetry endpoint. The issue is fixed in version 1.17.1 by implementing argument redaction.
Affected products
- dbt-labs dbt-mcp < 1.17.1
Identifiers
- CVE-2026-44970
- GHSA-jj54-r8gm-2fcf
- PYSEC-2026-2442
Timeline
- 2026-05-05: patched: Fix committed and version 1.17.1 released.
- 2026-05-13: advisory: GitHub Security Advisory published.
- 2026-07-16: disclosed: CVE published to NVD.