CVE-2026-44970

MEDIUMNVD 4.34.3—
EchelonGraph scoreMEDIUM confidence

This medium-severity CVE scores 4.3 under NVD CVSS v3. EPSS exploit probability: 0.4%, top 70% 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
Elevated
4.3EG
EchelonGraph verdictMonitorLow exploitation likelihood right now — keep watching.
  • Lower severity and no public exploit yet
CISA-KEV: Not listedEPSS PROB: 0%CVSS: 4.3Exploit: Elevated riskExposed: 0

No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.

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.

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 computed
Severity43% × 45%
Exploitation40% × 40%
Automatability0% × 15%
Action: Routine — remediate on your standard cadence.
EPSS PROB
0%
EPSS %ILE
31%
KEV
Not listed

Published

July 16, 2026

Last Modified

July 21, 2026

Advisory Details (4)

Auto-updated Jul 26, 2026
🔬 Proof of concept available. Patch available. Sources: github_commit, github_pr, github_release, github.
github Patch Available🟡 PoC Available

All MCP Tool Arguments Including Raw SQL and --vars Credentials Transmitted to dbt Labs Telemetry by Default Without Redaction · Advisory · dbt-labs/dbt-mcp · GitHub

https://github.com/dbt-labs/dbt-mcp/security/advisories/GHSA-jj54-r8gm-2fcf
github_release Patch Available

v1.17.1

Patch available: dbt-labs/dbt-mcp v1.17.1

https://github.com/dbt-labs/dbt-mcp/releases/tag/v1.17.1
github_pr Patch Available

fix: improve input validation and logging for dbt CLI tool parameters

Patch available: dbt-labs/dbt-mcp v1.17.1 (PR #752 merged 2026-05-05)

https://github.com/dbt-labs/dbt-mcp/pull/752
github_commit Patch Available

commit 6534507b5e7a (dbt-labs/dbt-mcp)

Patch available: dbt-labs/dbt-mcp v1.17.1 (contains commit 6534507b5e7a)

https://github.com/dbt-labs/dbt-mcp/commit/6534507b5e7a729758d5baece155602cad0bb22f

Affected Packages

(1 across 1 ecosystem)
PyPI(1)
PackageVulnerable rangeFixed inDependents
dbt-mcp0.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 8× in last 7d / 40× 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.

  1. 2026-09-11 14:53 UTCEPSS rescore
  2. 2026-09-11 09:37 UTCEPSS rescore
  3. 2026-09-10 09:34 UTCEPSS rescore
  4. 2026-09-08 22:00 UTCEPSS rescore
  5. 2026-09-08 00:27 UTCEG score recompute
  6. 2026-09-07 16:01 UTCEPSS rescore
  7. 2026-09-06 13:47 UTCEPSS rescore
  8. 2026-09-05 20:37 UTCEG score recompute
  9. 2026-09-04 05:06 UTCEPSS rescore
  10. 2026-09-02 14:12 UTCEPSS rescore
  11. 2026-09-01 13:54 UTCEPSS rescore
  12. 2026-08-31 03:56 UTCEG score recompute
  13. 2026-08-30 19:17 UTCEPSS rescore
  14. 2026-08-30 03:32 UTCEG score recompute
  15. 2026-08-30 01:22 UTCEPSS rescore
  16. 2026-08-28 21:41 UTCEPSS rescore
  17. 2026-08-28 03:00 UTCEG score recompute
  18. 2026-08-27 14:25 UTCEPSS rescore
  19. 2026-08-27 02:38 UTCEG score recompute
  20. 2026-08-26 14:46 UTCEPSS rescore
  21. 2026-08-26 02:11 UTCEG score recompute
  22. 2026-08-25 13:49 UTCEPSS rescore
  23. 2026-08-25 01:45 UTCEG score recompute
  24. 2026-08-22 00:37 UTCEG score recompute
  25. 2026-08-21 23:49 UTCEPSS rescore
Show 60 more
  1. 2026-08-21 00:15 UTCEG score recompute
  2. 2026-08-20 22:55 UTCEPSS rescore
  3. 2026-08-19 23:53 UTCEG score recompute
  4. 2026-08-19 17:04 UTCEPSS rescore
  5. 2026-08-18 21:53 UTCEG score recompute
  6. 2026-08-18 13:48 UTCEPSS rescore
  7. 2026-08-17 21:18 UTCEG score recompute
  8. 2026-08-17 13:47 UTCEPSS rescore
  9. 2026-08-16 19:16 UTCEG score recompute
  10. 2026-08-16 14:56 UTCEPSS rescore
  11. 2026-08-16 02:14 UTCEPSS rescore
  12. 2026-08-15 18:54 UTCEG score recompute
  13. 2026-08-15 01:30 UTCEPSS rescore
  14. 2026-08-14 18:32 UTCEG score recompute
  15. 2026-08-13 22:00 UTCEPSS rescore
  16. 2026-08-12 17:48 UTCEG score recompute
  17. 2026-08-12 13:51 UTCEPSS rescore
  18. 2026-08-11 17:27 UTCEG score recompute
  19. 2026-08-11 00:00 UTCEPSS rescore
  20. 2026-08-09 16:43 UTCEG score recompute
  21. 2026-08-09 13:46 UTCEPSS rescore
  22. 2026-08-08 16:37 UTCEPSS rescore
  23. 2026-08-08 16:22 UTCEG score recompute
  24. 2026-08-06 15:38 UTCEG score recompute
  25. 2026-08-06 13:46 UTCEPSS rescore
  26. 2026-08-05 19:17 UTCEPSS rescore
  27. 2026-08-05 15:04 UTCEG score recompute
  28. 2026-08-04 15:10 UTCEPSS rescore
  29. 2026-08-04 14:43 UTCEG score recompute
  30. 2026-08-04 10:38 UTCEPSS rescore
  31. 2026-08-02 14:00 UTCEG score recompute
  32. 2026-08-02 02:27 UTCEPSS rescore
  33. 2026-08-01 13:38 UTCEG score recompute
  34. 2026-08-01 04:16 UTCEPSS rescore
  35. 2026-07-31 13:16 UTCEG score recompute
  36. 2026-07-30 16:28 UTCEPSS rescore
  37. 2026-07-30 12:55 UTCEG score recompute
  38. 2026-07-30 01:30 UTCEPSS rescore
  39. 2026-07-29 12:32 UTCEG score recompute
  40. 2026-07-28 15:36 UTCEPSS rescore
  41. 2026-07-28 12:10 UTCEG score recompute
  42. 2026-07-27 14:13 UTCEPSS rescore
  43. 2026-07-27 11:47 UTCEG score recompute
  44. 2026-07-26 14:54 UTCEPSS rescore
  45. 2026-07-26 14:54 UTCEPSS rescore
  46. 2026-07-26 11:25 UTCEG score recompute
  47. 2026-07-25 14:18 UTCEPSS rescore
  48. 2026-07-24 14:17 UTCEPSS rescore
  49. 2026-07-23 14:18 UTCEPSS rescore
  50. 2026-07-23 03:15 UTCEG score recompute▲ 1.20
  51. 2026-07-22 14:08 UTCEPSS rescore
  52. 2026-07-21 17:18 UTCNVD updateCVSS v3 → 4.3 · severity → MEDIUM
  53. 2026-07-21 15:24 UTCEPSS rescore
  54. 2026-07-20 17:08 UTCEPSS rescore
  55. 2026-07-19 14:31 UTCEPSS rescore
  56. 2026-07-19 02:34 UTCEG score recompute
  57. 2026-07-19 02:29 UTCEPSS rescore
  58. 2026-07-18 10:04 UTCEPSS rescore
  59. 2026-07-16 17:54 UTCEG score recompute
  60. 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 0% probability of exploitation in the next 30 days, which ranks it in the top 69.4% of all scored CVEs.
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

Explore →

Is Your Infrastructure Affected by CVE-2026-44970?

EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.

Start Free Scan →Browse All CVEs