Signal is active with 2 mentions in latest observed window
Recommended action window: Monitor and triage in normal cycle
NVD 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.
Priority
LOW
Exploitation
NONE
PoC
YES
Patch
AVAILABLE
Momentum
NONE
If you run products in this scope, you should treat this CVE as relevant to your environment.
CVE-2026-44969 dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, http://DbtMCP.call_tool() in src/dbt_mcp/mcp/server.py logged the raw arguments diction… https://www.cve.org/CVERecord?id=CVE-2026-44969
Post summary
The post announces CVE-2026-44969, noting that before version 1.17.1 the dbt-mcp server logged raw arguments, but it provides no proof of concept, exploit, or mitigation information.
🚨*CVE* CVE-2026-44969 dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, http://DbtMCP.call_tool() in src/dbt_mcp/mcp/server.py logged the raw arguments diction… https://www.cve.org/CVERecord?id=CVE-2026-44969 ----- Traducción: CVE-20… http://infoflow.cloud`
Post summary
The post announces that dbt-mcp versions before 1.17.1 expose raw function arguments in logs, potentially leaking sensitive data, and indicates that updating to 1.17.1 resolves the issue.
1 of 1 entries
| Part | Vendor | Product | Version | Target SW | Target HW |
|---|---|---|---|---|---|
| App | getdbt | dbt_mcp_server | - | - | - |