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.
CVE-2026-44970
MEDIUMNVD 4.34.3—Trending — 4 sources updated this weekElevated
EchelonGraph scoreMEDIUM confidence
This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.2%, top 88% of all CVEs by exploit prediction. GitHub Security Advisory data not yet ingested — confidence will rise once GHSA publishes (typical lag: hours to days for open-source ecosystem CVEs; never for infrastructure-only CVEs).
Triggered by: NVD CVSS baseline
Sources: epss, nvd
4.3
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
- Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS: 0%CVSS: 4.3Exploit: NoneExposed: 0
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 4.3
- EG Score
- 4.3(medium)
- EG Risk
- 35(Track)EG Risk 35/100SSVC: Track
EG Risk is EchelonGraph's 0–100 priority score: it fuses intrinsic severity with real-world exploitation and automatability so you can rank equal-severity CVEs and fix the most dangerous first. Higher = act sooner. Distinct from the 0–10 EG Score (severity).
How it’s computedSeverity43% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 12.3%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 21, 2026
References (5)
- security-advisories@githubhttps://github.com/dbt-labs/dbt-mcp/commit/6534507b5e7a729758d5baece155602cad0bb22f
- security-advisories@githubhttps://github.com/dbt-labs/dbt-mcp/pull/752
- security-advisories@githubhttps://github.com/dbt-labs/dbt-mcp/releases/tag/v1.17.1
- security-advisories@githubhttps://github.com/dbt-labs/dbt-mcp/security/advisories/GHSA-jj54-r8gm-2fcf
- 134c704f-9b21-4f2e-91b3-4a467353bcc0https://github.com/dbt-labs/dbt-mcp/security/advisories/GHSA-jj54-r8gm-2fcf
Affected Packages
(1 across 1 ecosystem)
PyPI(1)
| Package | Vulnerable range | Fixed in | Dependents |
|---|---|---|---|
| dbt-mcp | 0.0.1a1 ... 1.9.3 (69 versions) | 1.17.1 | — |
Weakness Classification(1)
MITRE Common Weakness Enumeration — the root-cause categories this CVE belongs to.
Data Freshness Timeline
(refreshed 12× in last 7d / 12× in last 30d)
Each row is a source pipeline that fetched or updated this CVE on that date, with what changed. For example, "NVD update" means NVD published or revised its analysis for this CVE; "MITRE cvelistV5" means we ingested or refreshed it from the CNA feed. Most recent first.
- 2026-07-23 14:18 UTCEPSS rescore
- 2026-07-23 03:15 UTCEG score recompute▲ 1.20
- 2026-07-22 14:08 UTCEPSS rescore
- 2026-07-21 17:18 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
- 2026-07-21 15:24 UTCEPSS rescore
- 2026-07-20 17:08 UTCEPSS rescore
- 2026-07-19 14:31 UTCEPSS rescore
- 2026-07-19 02:34 UTCEG score recompute
- 2026-07-19 02:29 UTCEPSS rescore
- 2026-07-18 10:04 UTCEPSS rescore
- 2026-07-16 17:54 UTCEG score recompute
- 2026-07-16 17:53 UTCMITRE cvelistV5first tracked
Frequently asked(5)
What is CVE-2026-44970?
CVE-2026-44970 is a medium vulnerability published on July 16, 2026. dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, DefaultUsageTracker.emittoolcalledevent() in src/dbtmcp/tracking/tracking.py serialized every MCP tool call's complete arguments dictionary and sent it through dbtlabsvortex.producer.logproto without redaction,…
When was CVE-2026-44970 disclosed?
CVE-2026-44970 was first published in the National Vulnerability Database on July 16, 2026, with the most recent update on July 21, 2026. EchelonGraph re-ingests CVE updates from NVD on a 2-hour cycle, so this page reflects the latest published state.
Is CVE-2026-44970 actively exploited?
CVE-2026-44970 is not currently on CISA's Known Exploited Vulnerabilities catalog. FIRST EPSS estimates a 12.3% percentile likelihood of exploitation in the next 30 days — higher percentiles indicate greater predicted risk.
What is the CVSS score of CVE-2026-44970?
CVE-2026-44970 has a CVSS v3 base score of 4.3 (NVD).
How do I remediate CVE-2026-44970?
Patch to the fixed version published by the affected vendor. Where vendor advisories exist for CVE-2026-44970, EchelonGraph cross-links them in the Vendor Advisories panel below — those typically contain the canonical remediation steps, fixed version numbers, and any vendor-specific mitigations.
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44970
Is Your Infrastructure Affected by CVE-2026-44970?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.