Security readout for executives and security teams
Plain-English summary
dbt-mcp versions before 1.17.1 could send full tool arguments to dbt Labs telemetry by default. That may include raw SQL, dbt vars, credentials placed in vars, and model selection details. The business impact is unintended disclosure of sensitive development or analytics information, not system takeover.
Executive priority
Treat as a targeted confidentiality cleanup, not an emergency outage event. Prioritize upgrade and credential review where dbt-mcp is used with sensitive vars or SQL in regulated, customer, or production analytics environments.
Technical view
DefaultUsageTracker.emit_tool_called_event() serialized complete MCP tool-call arguments and sent them through dbtlabs_vortex.producer.log_proto without redaction. Telemetry was enabled by default unless DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 was set. The issue affects dbt-labs dbt-mcp before 1.17.1 and is fixed in 1.17.1.
Likely exposure
Exposure is limited to organizations running dbt-mcp before 1.17.1 with usage tracking enabled and sensitive values present in MCP tool arguments. Highest concern is teams passing secrets through --vars or embedding sensitive data in raw SQL queries.
Exploitation context
The provided sources do not show active exploitation, and the CVE is not listed as KEV. This is primarily a confidentiality issue caused by default telemetry behavior, with CVSS 3.1 score 3.1 and low severity.
Researcher notes
Evidence points to argument-level telemetry overcollection before 1.17.1. The source bundle identifies affected fields, default telemetry controls, fix version, CWE-201, and CVSS vector. No source confirms exploitation or broader affected products.
Mitigation direction
- Upgrade dbt-mcp to version 1.17.1 or later.
- Disable telemetry with DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 if upgrade is delayed.
- Review whether secrets were passed through --vars while telemetry was enabled.
- Rotate credentials that may have been transmitted in tool arguments.
- Follow dbt Labs advisory and release guidance for any additional steps.
Validation and detection
- Inventory dbt-mcp deployments and confirm versions are 1.17.1 or later.
- Check runtime configuration for telemetry opt-out environment variables.
- Review historical tool usage for sensitive sql_query, vars, or node_selection values.
- Confirm teams do not pass credentials through dbt vars.
- Document affected systems and remediation status for audit follow-up.
Public sources used
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
CWE-201: Information exposure and cloud metadata lookup
Information exposure and SSRF weaknesses can make discovery, cloud metadata, and credential material review relevant. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
Open ATT&CK lookupCVE-2026-44970 mapping review
Open the CVE-to-ATT&CK bridge for reviewed, inferred, or future official mappings tied to this CVE.
Open ATT&CK lookup- Severity
- Low
- CVSS
- 3.1 (3.1)
- Known Exploited
- No
- Published
Vector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
CNA and ADP enrichment extracted from CVE v5
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
SSVC decision data
CVSS vector scores
1 official scoreWe collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N1.61.4GitHub_MVulnerability scoring details
Base CVSS 3.1 score
3.1LowVector: CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N
Vulnerability timeline
Timeline events are normalized from CVE metadata, CNA source timelines, ADP timelines, and KEV metadata when present.
- CVE reservedCVE Program
The CVE ID was reserved by the assigning CNA.
- CVE publishedCVE Program
The CVE record was published.
- CVE updatedCVE Program
The CVE record metadata indicates this as the latest update time.
ADP provider summaries
Source materials
- CVE List V5 sourceCVE List V5
- https://github.com/dbt-labs/dbt-mcp/security/advisories/GHSA-jj54-r8gm-2fcfCVE reference, GitHub_M · x_refsource_CONFIRM
- https://github.com/dbt-labs/dbt-mcp/pull/752CVE reference, GitHub_M · x_refsource_MISC
- https://github.com/dbt-labs/dbt-mcp/commit/6534507b5e7a729758d5baece155602cad0bb22fCVE reference, GitHub_M · x_refsource_MISC
- https://github.com/dbt-labs/dbt-mcp/releases/tag/v1.17.1CVE reference, GitHub_M · x_refsource_MISC
Products and packages named in the record
CWE details
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
Insertion of Sensitive Information Into Sent Data
Insertion of Sensitive Information Into Sent Data represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.