# CVE-2026-44969: dbt MCP Server Logs Tool Arguments Including SQL Queries and Credentials in Plaintext Without Redaction When File Logging Is Enabled

> Attackers with file access can read sensitive SQL queries and credentials from logs when file logging is enabled in dbt-mcp.

- **Severity:** Low 2.5 (`CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Local or same network only
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 16 Jul 2026
- **Updated:** 17 Jul 2026
- **Also known as:** GHSA-7xgw-6qf3-7w59, PYSEC-2026-2441

## What is CVE-2026-44969?

CVE-2026-44969 is a low-severity vulnerability in dbt-labs dbt-mcp, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.

### Official description

dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, DbtMCP.call_tool() in src/dbt_mcp/mcp/server.py logged the raw arguments dictionary at INFO level before each tool call and at ERROR level on exceptions, and configure_file_logging() wrote those records to dbt-mcp.log when DBT_MCP_SERVER_FILE_LOGGING=true, preserving sensitive sql_query, vars, and node_selection values in plaintext without automatic rotation or deletion. This issue is fixed in version 1.17.1.

Weakness: CWE-532 (Insertion of Sensitive Information into Log File)

## Which versions are affected by CVE-2026-44969?

3 open source packages ship an affected version, including dbt-mcp. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `dbt-mcp` | PyPI | All versions | 1.17.1 |
| `dbt-mcp` | PyPI | All versions | 1.17.1 |
| `dbt-mcp` | PyPI | All versions | 1.17.1 |

Products: Getdbt Dbt Mcp Server.

## How do I fix CVE-2026-44969?

Upgrade dbt-mcp to 1.17.1 or later.

## Is CVE-2026-44969 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44969 exists.

## Other vulnerabilities in dbt-labs dbt-mcp

- [CVE-2026-44968](https://insights.sbomify.com/CVE-2026-44968/): dbt-mcp: Argument Injection in dbt CLI Tool Wrappers via node_selection and resource_type Parameters (medium 6.3)
- [CVE-2026-44970](https://insights.sbomify.com/CVE-2026-44970/): dbt MCP Server Transmits All MCP Tool Arguments Including Raw SQL and --vars Credentials to dbt Labs Telemetry by Default Without Redaction (low 3.1)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-44969 and fix it if it is affected.

What it is: CVE-2026-44969 is a low-severity vulnerability in dbt-labs dbt-mcp, published on 16 Jul 2026. It can only be exploited from the same machine or local network, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-44969 exists.

Affected packages and fixed versions:
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1
- dbt-mcp (PyPI): affected all versions; fixed in 1.17.1

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-44969/ (Markdown: https://insights.sbomify.com/CVE-2026-44969/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-44969
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-44969
- OSV: https://osv.dev/vulnerability/CVE-2026-44969

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-44969/
Summaries are generated and may contain mistakes; the official description above is the record.