dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, _run_dbt_command() in src/dbt_mcp/dbt_cli/tools.py appended unsanitized node_selection and resource_type values to the dbt subprocess argument list, allowing an MCP client to inject dbt global flags such as --profiles-dir, --project-dir, and --target into subprocess.Popen even though shell=False prevents shell metacharacter injection. This issue is fixed in version 1.17.1.
CVE-2026-44968
This medium-severity CVE scores 6.3 under a secondary CVSS source (NVD's own analysis pending). EPSS exploit probability: 0.2%, top 95% 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).
- Lower severity and no public exploit yet
No vendor fix yet — apply a workaround or compensating control (WAF / firewall / segmentation) and watch for a patch.
- CVSS v3
- 6.3
- EG Score
- 6.3(medium)
- EG Risk
- 44(Track)EG Risk 44/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 computedSeverity63% × 45%Exploitation40% × 40%Automatability0% × 15%Action: Routine — remediate on your standard cadence. - EPSS
- 4.7%
- KEV
- Not listed
Published
July 16, 2026
Last Modified
July 21, 2026
Advisory Details (1)
Auto-updated Jul 16, 2026Argument Injection in dbt CLI Tool Wrappers via node_selection and resource_type Parameters · Advisory · dbt-labs/dbt-mcp · GitHub
https://github.com/dbt-labs/dbt-mcp/security/advisories/GHSA-xpww-f6pm-cfhqAffected 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 9× in last 7d / 11× 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
- 2026-07-22 14:08 UTCEPSS rescore
- 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
Related CVEs(same CWE)
Same CWE
10 shownCWE-88
- CVE-2018-3856EG 9.9CRITICAL
- CVE-2020-28026EG 9.8EPSS 95%CRITICAL
- CVE-2020-21224EG 9.8EPSS 98%CRITICAL
- CVE-2020-25494EG 9.8EPSS 98%CRITICAL
- CVE-2020-5648EG 9.8CRITICAL
- CVE-2020-15692EG 9.8EPSS 90%CRITICAL
- CVE-2020-5599EG 9.8CRITICAL
- CVE-2020-12641EG 9.8 KEVEPSS 100%CRITICAL
- CVE-2019-12148EG 9.8CRITICAL
- CVE-2019-12147EG 9.8CRITICAL
Frequently asked(5)
What is CVE-2026-44968?
When was CVE-2026-44968 disclosed?
Is CVE-2026-44968 actively exploited?
What is the CVSS score of CVE-2026-44968?
How do I remediate CVE-2026-44968?
Dependency Blast Radius
See which npm, PyPI, Go, and Maven packages are affected by CVE-2026-44968
Is Your Infrastructure Affected by CVE-2026-44968?
EchelonGraph automatically scans your cloud infrastructure and maps CVE exposure using blast radius analysis.