Quick answers
- Is CVE-2026-44968 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-44968 being exploited in the wild.
- How severe is CVE-2026-44968?
- Medium severity, with a CVSS score of 6.3, published 16 July 2026.
- Which products and versions are affected?
- dbt-mcp (PyPI) <= 1.17.0, ECOSYSTEM:introduced=0,fixed=1.17.1.
- Is there a fix for CVE-2026-44968?
- Yes. dbt-mcp (PyPI): upgrade to 1.17.1 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
- How is CVE-2026-44968 attacked?
- It is attacked with local access, in a software library.
- Am I affected by CVE-2026-44968?
- Check whether you run dbt-mcp (PyPI) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
How to fix
- dbt-mcp (PyPI): upgrade to 1.17.1 or later
pip install "dbt-mcp>=1.17.1"
Technical details
An argument injection vulnerability (CWE-88) exists in dbt-mcp's `_run_dbt_command()` function within `src/dbt_mcp/dbt_cli/tools.py`. The application fails to sanitize the `node_selection` and `resource_type` parameters before appending them to the argument list for `subprocess.Popen`. While `shell=False` is used, the lack of validation allows an attacker to provide strings starting with hyphens (e.g., `--profiles-dir` or `--target`), which the underlying dbt process interprets as global flags rather than positional arguments. This can be exploited by a local attacker to point dbt to a malicious configuration file, potentially leading to arbitrary code execution or data exfiltration via malicious database drivers. The issue is fixed in version 1.17.1 by validating that input tokens do not start with dashes and verifying resource types against an allowlist.
Affected products
- dbt-labs dbt-mcp < 1.17.1
Identifiers
- CVE-2026-44968
- GHSA-xpww-f6pm-cfhq
- PYSEC-2026-2444
Timeline
- 2026-05-05: patched: Fix committed and version 1.17.1 released.
- 2026-05-13: advisory: GitHub Security Advisory GHSA-xpww-f6pm-cfhq published.
- 2026-07-16: disclosed: CVE-2026-44968 published to NVD.