CVE-2026-44969
Received Received - Intake

dbt-mcp Information Disclosure via Logged Arguments

Publication date: 2026-07-16

Last updated on: 2026-07-16

Assigner: GitHub, Inc.

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.

CVSS Scores

EPSS Scores

Probability:
Percentile:

Meta Information

Published
2026-07-16
Last Modified
2026-07-16
Generated
2026-07-16
AI Q&A
2026-07-16
EPSS Evaluated
N/A
NVD
CVE-2026-44969
EUVD
EUVD-2026-44993

Affected Vendors & Products

Showing 3 associated CPEs
Vendor Product Version / Range
dbt_mcp dbt_mcp to 1.17.1 (exc)
dbt-labs dbt-mcp to 1.17.1 (exc)
dbt-labs dbt-mcp From 1.17.0 (inc)

Helpful Resources

Exploitability

CWE
CWE Icon
KEV
KEV Icon
CWE ID Description
CWE-532 The product writes sensitive information to a log file.

Attack-Flow Graph

AI Quick Actions

Instant insights powered by AI
Executive Summary

CVE-2026-44969 is a vulnerability in dbt-mcp versions before 1.17.1 where sensitive data like SQL queries, credentials, and node selections are logged in plaintext without redaction. The logging occurs in the call_tool() function and when file logging is enabled via DBT_MCP_SERVER_FILE_LOGGING=true, these logs are written to dbt-mcp.log without automatic rotation or deletion.

Detection Guidance

Check for the presence of dbt-mcp versions <= 1.17.0 by running: pip show dbt-mcp. If installed, verify if DBT_MCP_SERVER_FILE_LOGGING=true is set in environment variables. Inspect dbt-mcp.log in the project root for plaintext sensitive data like SQL queries or credentials.

Impact Analysis

This vulnerability can expose sensitive information such as SQL queries, credentials, and node selections stored in logs. Attackers with local access could read these logs and gain unauthorized access to systems or data. The impact includes potential theft of personally identifiable information (PII) and credentials.

Compliance Impact

This vulnerability could lead to non-compliance with GDPR and HIPAA due to the exposure of sensitive personal data and credentials in plaintext logs. Regulations require protection of such data, and improper logging practices may result in violations and associated penalties.

Mitigation Strategies

Upgrade dbt-mcp to version 1.17.1 or later. Disable file logging by setting DBT_MCP_SERVER_FILE_LOGGING=false. Review and redact any existing dbt-mcp.log files containing sensitive data. Set log level to WARNING to avoid persisting normal-operation logs.

Chat Assistant

Ask questions about this CVE
Hi! I’m here to help you understand CVE-2026-44969. Ask me anything about the vulnerability, its impact, or mitigation strategies.
0/70

EPSS Chart