How severe is CVE-2026-44970?

CVE-2026-44970 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.

Is CVE-2026-44970 being actively exploited?

It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.

What products are affected by CVE-2026-44970?

CVE-2026-44970 affects Getdbt Dbt Mcp Server. See the affected-products list for the exact vulnerable versions.

How do I fix CVE-2026-44970?

Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.

When was CVE-2026-44970 published?

CVE-2026-44970 was published on 2026-07-16 and last updated on 2026-07-21.

CVE-2026-44970

CVE-2026-44970 is a low-severity vulnerability in Getdbt Dbt Mcp Server with a CVSS 3.x base score of 3.1. It is not currently listed as actively exploited by CISA, and its EPSS exploit-prediction score is low. The underlying weakness is classified as CWE-201.

Key facts

Severity: Low (CVSS 3.x base score 3.1)
EPSS exploit prediction: 0% (31st percentile)
Actively exploited: Not listed in CISA KEV
Weakness: CWE-201
Affected product: Getdbt Dbt Mcp Server
Published: 2026-07-16
Last modified: 2026-07-21

Description

dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, DefaultUsageTracker.emit_tool_called_event() in src/dbt_mcp/tracking/tracking.py serialized every MCP tool call's complete arguments dictionary and sent it through dbtlabs_vortex.producer.log_proto without redaction, including sql_query from show, vars from run, build, and test, and node_selection from compile, while usage_tracking_enabled in settings.py enabled telemetry by default unless DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 was set. This issue is fixed in version 1.17.1.

Frequently asked questions

What is CVE-2026-44970?: dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, DefaultUsageTracker.emit_tool_called_event() in src/dbt_mcp/tracking/tracking.py serialized every MCP tool call's complete arguments dictionary and sent it through dbtlabs_vortex.producer.log_proto without redaction, including sql_query from show, vars from run, build, and test, and node_selection from compile, while usage_tracking_enabled in settings.py enabled telemetry by default unless DBT_SEND_ANONYMOUS_USAGE_STATS=false or DO_NOT_TRACK=1 was set. This issue is fixed in version 1.17.1.
How severe is CVE-2026-44970?: CVE-2026-44970 has a CVSS 3.x base score of 3.1, rated low severity. It is exploitable over network with high attack complexity, requires low privileges and no user interaction. Impact on confidentiality is low, integrity none, and availability none.
Is CVE-2026-44970 being actively exploited?: It is not currently listed in CISA's KEV catalog. Its EPSS exploit-prediction score is 0% (31st percentile), an estimate of the probability of exploitation in the next 30 days.
What products are affected by CVE-2026-44970?: CVE-2026-44970 affects Getdbt Dbt Mcp Server. See the affected-products list for the exact vulnerable versions.
How do I fix CVE-2026-44970?: Review the linked vendor and NVD advisories for patched versions and mitigations, then upgrade or apply the recommended workaround.
When was CVE-2026-44970 published?: CVE-2026-44970 was published on 2026-07-16 and last updated on 2026-07-21.

References

Affected products (1)

cpe:2.3:a:getdbt:dbt_mcp_server:*:*:*:*:*:*:*:*

More vulnerabilities in Getdbt Dbt Mcp Server

CVE-2026-44968 — Medium (CVSS 6.3): dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, _run_dbt_command() in…
CVE-2026-44969 — Low (CVSS 2.5): dbt-mcp is a Model Context Protocol server for interacting with dbt. Prior to 1.17.1, DbtMCP.call_tool() in…

All CVEs affecting Getdbt Dbt Mcp Server →

Other CWE-201 vulnerabilities

CVE-2025-49408 — Critical (CVSS 10.0): Insertion of Sensitive Information Into Sent Data vulnerability in WPDeveloper Templately allows Retrieve Embedded…
CVE-2024-7205 — Critical (CVSS 9.4): When the device is shared, the homepage module are before 2.19.0 in eWeLink Cloud Service allows Secondary user to…
CVE-2026-8924 — Critical (CVSS 9.1): A flaw in curl’s cookie parsing logic allows a malicious HTTP server to set "super cookies" that bypass the Public…
CVE-2026-39912 — Critical (CVSS 9.1): V2Board 1.6.1 through 1.7.4 and Xboard through 0.1.9 expose authentication tokens in HTTP response bodies of the…
CVE-2025-48749 — Critical (CVSS 9.1): Netwrix Directory Manager (formerly Imanami GroupID) v11.0.0.0 and before & after v.11.1.25134.03 inserts Sensitive…
CVE-2025-11500 — High (CVSS 8.7): Tinycontrol devices such as tcPDU and LAN Controllers LK3.5, LK3.9 and LK4 have two separate authentication…

Browse all CWE-201 vulnerabilities →