Skip to main content
Press slash or control plus K to focus the search. Use the arrow keys to navigate results and press enter to open a threat.
Reconnecting to live updates…

CVE-2026-44969: CWE-532: Insertion of Sensitive Information into Log File in dbt-labs dbt-mcp

0
Low
VulnerabilityCVE-2026-44969cvecve-2026-44969cwe-532
Published: 07/16/2026 (07/16/2026, 17:49:50 UTC)
Source: CVE Database V5
Vendor/Project: dbt-labs
Product: 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 log files when file logging is enabled. This logging occurs at INFO level before tool calls and at ERROR level on exceptions, potentially exposing sensitive data. The issue is fixed in version 1.17.1.

CVSS v3.1

Score 2.5low

Attack Vector
Local
Attack Complexity
High
Privileges Required
Low
User Interaction
None
Scope
Unchanged
Confidentiality
Low
Integrity
None
Availability
None
CVSS:3.1/AV:L/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

Affected software

dbt-mcp
pkg:pypi/dbt-mcp
Affected versions
<1.17.1

Run on your own infrastructure? Check whether these packages are installed with threat-finder — our free open-source scanner.

AI-Powered Analysis

Machine-generated threat intelligence

AILast updated: 07/16/2026, 18:17:38 UTC

Technical Analysis

The vulnerability in dbt-mcp (CVE-2026-44969) involves the insertion of sensitive information into log files. Specifically, the DbtMCP.call_tool() function logs the raw arguments dictionary, including sensitive fields like sql_query, vars, and node_selection, at INFO and ERROR levels. 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, risking exposure of sensitive data. This behavior was corrected in version 1.17.1.

Potential Impact

Sensitive information is recorded in plaintext in log files, which could lead to unauthorized disclosure if log files are accessed by unauthorized parties. The CVSS score of 2.5 reflects a low severity impact with limited confidentiality impact and no integrity or availability impact.

Mitigation Recommendations

Upgrade to dbt-mcp version 1.17.1 or later, where this logging behavior has been fixed. Until upgraded, avoid enabling file logging with DBT_MCP_SERVER_FILE_LOGGING=true to prevent sensitive data from being written to logs.

Pro Console: star threats, build custom feeds, automate alerts via Slack, email & webhooks.Upgrade to Pro

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/16/2026, 18:17:38 UTC

Last updated: 07/17/2026, 02:25:14 UTC

Views: 13

Community Reviews

0 reviews

Crowdsource mitigation strategies, share intel context, and vote on the most helpful responses. Sign in to add your voice and help keep defenders ahead.

Sort by
Loading community insights…

Want to contribute mitigation steps or threat intel context? Sign in or create an account to join the community discussion.

Actions

PRO

Updates to AI analysis require Pro Console access. Upgrade inside Console → Billing.

Please log in to the Console to use AI analysis features.

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

Breach by OffSeqOFFSEQFRIENDS — 25% OFF

Check if your credentials are on the dark web

Instant breach scanning across billions of leaked records. Free tier available.

Scan now
OffSeq TrainingCredly Certified

Lead Pen Test Professional

Technical5-day eLearningPECB Accredited
View courses