Skip to content

← Actionable
Low, CVSS 3.1amended

dbt MCP Server Transmits All MCP Tool Arguments Including Raw SQL and --vars Credentials to dbt Labs Telemetry by Default Without Redaction

CVE-2026-44970GHSA-jj54-r8gm-2fcf

What to do

Vendor fix available. Upgrade each affected package to the fixed version on its release line (dbt-mcp 1.17.1), redeploy, then verify what is actually installed.

This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.

Affected packages

  • PyPI dbt-mcp

    Affected
    <= 1.17.0
    Fixed in
    1.17.1

Sources

Severity and exploitation
Exploitation
No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
CVSS
3.1 · CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
EPSS
  • CVE-2026-44970: 0.37% estimated exploitation activity in the next 30 days; percentile 31.28 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description

As published by the source; long descriptions are shortened.

Discovered through manual source code review. Verified by PoC execution against a local dbt-mcp v1.15.1 installation. Summary DefaultUsageTracker.emittoolcalledevent() in src/dbtmcp/tracking/tracking.py serializes the complete arguments dictionary of every MCP tool call and transmits it verbatim to the dbt Labs telemetry service via dbtlabsvortex.producer.logproto. No field is redacted, truncated, or excluded before transmission. This includes the sqlquery parameter of the show tool (arbitrary SQL) and the vars parameter of run, build, and test (JSON string that may contain credentials). Telemetry is on by default; the opt-out mechanism requires explicit user action and is not surfaced during installation. Details Serialization code (tracking.py lines 101–103): Every key-value pair in arguments is JSON-serialized into argumentsmapping and passed to logproto(ToolCalled(...)). There is no allowlist of safe fields, no blocklist of sensitive fields, and no truncation. Default opt-out…

Dates and revisions
Published by the source
Last modified by the source
Source last checked
  1. Revision 2 · amended ·

    Amended from ghsa record GHSA-jj54-r8gm-2fcf

  2. Revision 1 · created ·

    Published from osv record GHSA-jj54-r8gm-2fcf

Agent brief

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-44970

Advisory: dbt MCP Server Transmits All MCP Tool Arguments Including Raw SQL and --vars Credentials to dbt Labs Telemetry by Default Without Redaction
IDs: CVE-2026-44970, GHSA-jj54-r8gm-2fcf
Record: https://patchnext.com/advisories/cve-2026-44970 (revision 2, source checked 26 Oct 2026, 13:41 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Low (CVSS 3.1)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: dbt-mcp 1.17.1. A vendor fix does not mean a deployment is fixed.

## Affected components
- PyPI dbt-mcp: affected <= 1.17.0; fixed in 1.17.1

## Suggested inspection (read-only)
- `python -m pip show dbt-mcp`: prints the installed version. Run with the environment that serves production active.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on dbt-mcp.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GHSA-jj54-r8gm-2fcf (OSV record GHSA-jj54-r8gm-2fcf lists affected ranges: PyPI dbt-mcp >=0 <1.17.1 (fixed))
- Verified: https://github.com/advisories/GHSA-jj54-r8gm-2fcf (GitHub-reviewed advisory GHSA-jj54-r8gm-2fcf lists affected ranges: PyPI dbt-mcp >=0 <=1.17.0)

Commands are suggestions: review each one before running it.

Loading voting…