https://cve.radiocsirt.org Contains only the most 10 recent entries. http://www.rssboard.org/rss-specification python-feedgen en Sat, 03 Oct 2026 11:26:55 +0000 https://cve.radiocsirt.org/vuln/cve-2026-44969 <p><strong>Affected:</strong> dbt-labs dbt-mcp</p> <p>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.</p> <p><strong>Affected:</strong> dbt-labs dbt-mcp</p> <p>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.</p> https://cve.radiocsirt.org/vuln/cve-2026-44969 https://cve.radiocsirt.org/vuln/ghsa-7xgw-6qf3-7w59 <p><strong>Affected:</strong> PyPI: dbt-mcp</p> <p>*Discovered through manual source code review. Verified by PoC execution against a local dbt-mcp v1.15.1 installation.*</p> <p>### Summary</p> <p>`DbtMCP.call_tool()` in `src/dbt_mcp/mcp/server.py` logs the complete raw `arguments` dictionary at `INFO` level on every tool invocation (line 67) and again at `ERROR` level if the call raises an exception (lines 77–79). No field is redacted before logging. When the documented `DBT_MCP_SERVER_FILE_LOGGING=true` feature is enabled, these log records are written to `dbt-mcp.log` in the project root directory as plaintext. Sensitive data — raw SQL queries, `--vars` payloads carrying credentials, node selectors — persists on disk indefinitely with no automatic rotation or deletion.</p> <p>### Details</p> <p>**Vulnerable log statements (`server.py`):**</p> <p>```python # Line 67 — emitted before every tool execution logger.info(f&#34;Calling tool: {name} with arguments: {arguments}&#34;)</p> <p># Lines 77–79 — emitted if the tool raises an exception (double-logging on failure) logger.error( f&#34;Error calling tool: {name} with arguments: {arguments} &#34; f&#34;in {end_time - start_time}ms: {e}&#34; ) ```</p> <p>`arguments` is the raw Python dict received from the MCP client. It is string-interpolated directly into the log message. On a tool call that raises an exception, the same dict is logged twice — once at INFO and once at ERROR.</p> <p>File logging is activated by `DBT_MCP_SERVER_FILE_LOGGING=true` (a documented feature in the project README). The log file location is resolved by `configure_…</p> <p><strong>Affected:</strong> PyPI: dbt-mcp</p> <p>*Discovered through manual source code review. Verified by PoC execution against a local dbt-mcp v1.15.1 installation.*</p> <p>### Summary</p> <p>`DbtMCP.call_tool()` in `src/dbt_mcp/mcp/server.py` logs the complete raw `arguments` dictionary at `INFO` level on every tool invocation (line 67) and again at `ERROR` level if the call raises an exception (lines 77–79). No field is redacted before logging. When the documented `DBT_MCP_SERVER_FILE_LOGGING=true` feature is enabled, these log records are written to `dbt-mcp.log` in the project root directory as plaintext. Sensitive data — raw SQL queries, `--vars` payloads carrying credentials, node selectors — persists on disk indefinitely with no automatic rotation or deletion.</p> <p>### Details</p> <p>**Vulnerable log statements (`server.py`):**</p> <p>```python # Line 67 — emitted before every tool execution logger.info(f&#34;Calling tool: {name} with arguments: {arguments}&#34;)</p> <p># Lines 77–79 — emitted if the tool raises an exception (double-logging on failure) logger.error( f&#34;Error calling tool: {name} with arguments: {arguments} &#34; f&#34;in {end_time - start_time}ms: {e}&#34; ) ```</p> <p>`arguments` is the raw Python dict received from the MCP client. It is string-interpolated directly into the log message. On a tool call that raises an exception, the same dict is logged twice — once at INFO and once at ERROR.</p> <p>File logging is activated by `DBT_MCP_SERVER_FILE_LOGGING=true` (a documented feature in the project README). The log file location is resolved by `configure_…</p> https://cve.radiocsirt.org/vuln/ghsa-7xgw-6qf3-7w59