CVE-2026-44969: CWE-532: Insertion of Sensitive Information into Log File in dbt-labs dbt-mcp
dbt-mcp versions prior to 1.17.1 log sensitive information such as sql_query, vars, and node_selection in plaintext to dbt-mcp.log when file logging is enabled. This occurs because the raw arguments dictionary is logged at INFO level before each tool call and at ERROR level on exceptions. The issue is fixed in version 1.17.1.
AI Analysis
Technical Summary
The vulnerability CVE-2026-44969 in dbt-labs dbt-mcp involves insertion of sensitive information into log files. Specifically, before version 1.17.1, the DbtMCP.call_tool() function logs the raw arguments dictionary at INFO and ERROR levels, which includes sensitive data like sql_query, vars, and node_selection. When file logging is enabled via the DBT_MCP_SERVER_FILE_LOGGING environment variable, these logs are written to dbt-mcp.log without automatic rotation or deletion, potentially exposing sensitive information. This logging behavior was corrected in version 1.17.1.
Potential Impact
Sensitive information such as SQL queries and variable values may be exposed in plaintext log files, potentially leading to information disclosure if unauthorized parties access these logs. The CVSS score of 2.5 reflects a low severity impact with limited confidentiality impact and no integrity or availability impact.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later, where this logging of sensitive information has been fixed. Until upgraded, avoid enabling file logging with DBT_MCP_SERVER_FILE_LOGGING=true or ensure strict access controls and log management to protect sensitive log contents. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the issue is fixed in version 1.17.1 as per the description.
CVE-2026-44969: CWE-532: Insertion of Sensitive Information into Log File in dbt-labs dbt-mcp
Description
dbt-mcp versions prior to 1.17.1 log sensitive information such as sql_query, vars, and node_selection in plaintext to dbt-mcp.log when file logging is enabled. This occurs because the raw arguments dictionary is logged at INFO level before each tool call and at ERROR level on exceptions. The issue is fixed in version 1.17.1.
CVSS v3.1
Score 2.5low
Affected software
Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.
Weaknesses
AI-Powered Analysis
Machine-generated threat intelligence
Technical Analysis
The vulnerability CVE-2026-44969 in dbt-labs dbt-mcp involves insertion of sensitive information into log files. Specifically, before version 1.17.1, the DbtMCP.call_tool() function logs the raw arguments dictionary at INFO and ERROR levels, which includes sensitive data like sql_query, vars, and node_selection. When file logging is enabled via the DBT_MCP_SERVER_FILE_LOGGING environment variable, these logs are written to dbt-mcp.log without automatic rotation or deletion, potentially exposing sensitive information. This logging behavior was corrected in version 1.17.1.
Potential Impact
Sensitive information such as SQL queries and variable values may be exposed in plaintext log files, potentially leading to information disclosure if unauthorized parties access these logs. The CVSS score of 2.5 reflects a low severity impact with limited confidentiality impact and no integrity or availability impact.
Mitigation Recommendations
Upgrade dbt-mcp to version 1.17.1 or later, where this logging of sensitive information has been fixed. Until upgraded, avoid enabling file logging with DBT_MCP_SERVER_FILE_LOGGING=true or ensure strict access controls and log management to protect sensitive log contents. Patch status is not explicitly stated as 'official-fix' in the vendor advisory, but the issue is fixed in version 1.17.1 as per the description.
Technical Details
- Data Version
- 5.2
- Assigner Short Name
- GitHub_M
- Date Reserved
- 2026-05-08T16:23:33.263Z
- Cvss Version
- 3.1
- State
- PUBLISHED
- Remediation Level
- null
Threat ID: 6a591cd868715ace4377affa
Added to database: 07/16/2026, 18:03:04 UTC
Last enriched: 07/23/2026, 22:40:19 UTC
Last updated: 08/29/2026, 00:20:45 UTC
Views: 82
Community Reviews
0 reviewsCrowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.
Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.
Actions
Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.
Need more coverage?
Upgrade to Pro Console for AI refresh and higher limits.
For incident response and remediation, OffSeq services can help resolve threats faster.
Latest Threats
Check if your credentials are on the dark web
Instant breach scanning across billions of leaked records. Free tier available.