CVE-2026-44969 is a low-severity security vulnerability in dbt-mcp (pip), affecting versions <= 1.17.0. It is fixed in 1.17.1.
Discovered through manual source code review. Verified by PoC execution against a local dbt-mcp v1.15.1 installation. Summary DbtMCP.calltool() in src/dbtmcp/mcp/server.py logs the complete raw arguments dictionary at INFO level on every tool invocation (line 67) and again at ERROR level if the call raises an exception (lines 77–79). No field is redacted before logging. When the documented DBTMCPSERVERFILELOGGING=true feature is enabled, these log records are written to dbt-mcp.log in the project root directory as plaintext. Sensitive data, raw SQL queries, --vars payloads carrying credentials, node selectors, persists on disk indefinitely with no automatic rotation or deletion. Details Vulnerable log statements (server.py): arguments is the raw Python dict received from the MCP client. It is string-interpolated directly into the log message. On a tool call that raises an exception, the same dict is logged twice, once at INFO and once at ERROR. File logging is activated by DBTMCPSERVERFILELOGGING=true (a documented feature in the project README). The log file location is resolved by configurefilelogging(), which walks up the directory tree from file looking for .git or pyproject.toml, falling back to $HOME. Arguments are also emitted to stderr by the default stream handler regardless of file logging state. PoC MCP client script, triggers real tool calls and verifies log file contents: Expected log file entries: log argument keys only: File logging: Consider reducing the default log level for the file handler to WARNING so that normal-operation INFO records (which include arguments) are not persisted. Sensitive content would only appear in file logs on error.
CVE-2026-44969 has a CVSS score of 2.5 (Low). The vector is requires local access, low privileges required, and no user interaction. A CVSS score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether this affects your application depends on whether the vulnerable code is present and reachable in your environment.
A fixed version is available (1.17.1). Upgrading removes the vulnerable code path.
pip
dbt-mcp (<= 1.17.0)dbt-mcp → 1.17.1 (pip)Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter instead of chasing every advisory.
Kodem's runtime-powered SCA identifies whether CVE-2026-44969 is reachable in your applications. Explore AI application security for your team.
See if CVE-2026-44969 is reachable in your applications. Get a demo
Upgrade dbt-mcp to 1.17.1 or later to resolve this vulnerability.
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
CVE-2026-44969 is a low-severity security vulnerability in dbt-mcp (pip), affecting versions <= 1.17.0. It is fixed in 1.17.1.
CVE-2026-44969 has a CVSS score of 2.5 (Low). This score reflects the worst-case severity of the vulnerability, not your specific exposure. Whether it represents real risk in your environment depends on whether the vulnerable code is present and reachable.
dbt-mcp (pip) versions <= 1.17.0 is affected.
Yes. CVE-2026-44969 is fixed in 1.17.1. Upgrade to this version or later.
Whether CVE-2026-44969 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
Upgrade dbt-mcp to 1.17.1 or later.