CVE-2026-44970 Vulnerability Analysis & Exploit Details

CVE-2026-44970
Vulnerability Scoring

3.1
/10
Moderate Risk

Exploiting CVE-2026-44970 requires specific conditions, leading to a moderate security impact.

Attack Complexity Details

  • Attack Complexity: High
    Exploits require significant effort and special conditions.
  • Attack Vector: Network
    Vulnerability is exploitable over a network without physical access.
  • Privileges Required: Low
    Some privileges are necessary to exploit the vulnerability.
  • Scope: Unchanged
    Exploit remains within the originally vulnerable component.
  • User Interaction: None
    No user interaction is necessary for exploitation.

CVE-2026-44970 Details

Status: Analyzed

Last updated: 🕓 21 Jul 2026, 16:04 UTC
Originally published on: 🕕 16 Jul 2026, 18:16 UTC

Time between publication and last update: 4 days

CVSS Release: version 3

CVSS3 Source

security-advisories@github.com

CVSS3 Type

Secondary

CVSS3 Vector

CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:L/I:N/A:N

CVE-2026-44970 Vulnerability Summary

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.

Assessing the Risk of CVE-2026-44970

Access Complexity Graph

The exploitability of CVE-2026-44970 depends on two key factors: attack complexity (the level of effort required to execute an exploit) and privileges required (the access level an attacker needs).

Exploitability Analysis for CVE-2026-44970

This vulnerability, CVE-2026-44970, requires a high level of attack complexity and low privileges, making it difficult but not impossible to exploit. Organizations should ensure robust security configurations to mitigate risks.

Understanding AC and PR

A lower complexity and fewer privilege requirements make exploitation easier. Security teams should evaluate these aspects to determine the urgency of mitigation strategies, such as patch management and access control policies.

Attack Complexity (AC) measures the difficulty in executing an exploit. A high AC means that specific conditions must be met, making an attack more challenging, while a low AC means the vulnerability can be exploited with minimal effort.

Privileges Required (PR) determine the level of system access necessary for an attack. Vulnerabilities requiring no privileges are more accessible to attackers, whereas high privilege requirements limit exploitation to authorized users with elevated access.

CVSS Score Breakdown Chart

Above is the CVSS Sub-score Breakdown for CVE-2026-44970, illustrating how Base, Impact, and Exploitability factors combine to form the overall severity rating. A higher sub-score typically indicates a more severe or easier-to-exploit vulnerability.

CIA Impact Analysis

Below is the Impact Analysis for CVE-2026-44970, showing how Confidentiality, Integrity, and Availability might be affected if the vulnerability is exploited. Higher values usually signal greater potential damage.

  • Confidentiality: Low
    CVE-2026-44970 could lead to minor leaks of non-critical information without major privacy breaches.
  • Integrity: None
    CVE-2026-44970 poses no threat to data integrity.
  • Availability: None
    CVE-2026-44970 does not impact system availability.

CVE-2026-44970 References

External References

CWE Common Weakness Enumeration

CWE-201

CAPEC Common Attack Pattern Enumeration and Classification

  • Choosing Message Identifier CAPEC-12 This pattern of attack is defined by the selection of messages distributed via multicast or public information channels that are intended for another client by determining the parameter value assigned to that client. This attack allows the adversary to gain access to potentially privileged information, and to possibly perpetrate other attacks through the distribution means by impersonation. If the channel/message being manipulated is an input rather than output mechanism for the system, (such as a command bus), this style of attack could be used to change the adversary's identifier to more a privileged one.
  • Exploiting Incorrectly Configured SSL/TLS CAPEC-217 An adversary takes advantage of incorrectly configured SSL/TLS communications that enables access to data intended to be encrypted. The adversary may also use this type of attack to inject commands or other traffic into the encrypted stream to cause compromise of either the client or server.
  • WiFi MAC Address Tracking CAPEC-612 In this attack scenario, the attacker passively listens for WiFi messages and logs the associated Media Access Control (MAC) addresses. These addresses are intended to be unique to each wireless device (although they can be configured and changed by software). Once the attacker is able to associate a MAC address with a particular user or set of users (for example, when attending a public event), the attacker can then scan for that MAC address to track that user in the future.
  • WiFi SSID Tracking CAPEC-613 In this attack scenario, the attacker passively listens for WiFi management frame messages containing the Service Set Identifier (SSID) for the WiFi network. These messages are frequently transmitted by WiFi access points (e.g., the retransmission device) as well as by clients that are accessing the network (e.g., the handset/mobile device). Once the attacker is able to associate an SSID with a particular user or set of users (for example, when attending a public event), the attacker can then scan for this SSID to track that user in the future.
  • Cellular Broadcast Message Request CAPEC-618 In this attack scenario, the attacker uses knowledge of the target’s mobile phone number (i.e., the number associated with the SIM used in the retransmission device) to cause the cellular network to send broadcast messages to alert the mobile device. Since the network knows which cell tower the target’s mobile device is attached to, the broadcast messages are only sent in the Location Area Code (LAC) where the target is currently located. By triggering the cellular broadcast message and then listening for the presence or absence of that message, an attacker could verify that the target is in (or not in) a given location.
  • Signal Strength Tracking CAPEC-619 In this attack scenario, the attacker passively monitors the signal strength of the target’s cellular RF signal or WiFi RF signal and uses the strength of the signal (with directional antennas and/or from multiple listening points at once) to identify the source location of the signal. Obtaining the signal of the target can be accomplished through multiple techniques such as through Cellular Broadcast Message Request or through the use of IMSI Tracking or WiFi MAC Address Tracking.
  • Analysis of Packet Timing and Sizes CAPEC-621 An attacker may intercept and log encrypted transmissions for the purpose of analyzing metadata such as packet timing and sizes. Although the actual data may be encrypted, this metadata may reveal valuable information to an attacker. Note that this attack is applicable to VOIP data as well as application data, especially for interactive apps that require precise timing and low-latency (e.g. thin-clients).
  • Electromagnetic Side-Channel Attack CAPEC-622 In this attack scenario, the attacker passively monitors electromagnetic emanations that are produced by the targeted electronic device as an unintentional side-effect of its processing. From these emanations, the attacker derives information about the data that is being processed (e.g. the attacker can recover cryptographic keys by monitoring emanations associated with cryptographic processing). This style of attack requires proximal access to the device, however attacks have been demonstrated at public conferences that work at distances of up to 10-15 feet. There have not been any significant studies to determine the maximum practical distance for such attacks. Since the attack is passive, it is nearly impossible to detect and the targeted device will continue to operate as normal after a successful attack.
  • Compromising Emanations Attack CAPEC-623 Compromising Emanations (CE) are defined as unintentional signals which an attacker may intercept and analyze to disclose the information processed by the targeted equipment. Commercial mobile devices and retransmission devices have displays, buttons, microchips, and radios that emit mechanical emissions in the form of sound or vibrations. Capturing these emissions can help an adversary understand what the device is doing.

Vulnerable Configurations

  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.3:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.3:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.4:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.4:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.5:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.5:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.6:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.6:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.7:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.7:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.8:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.8:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.9:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.9:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.10:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.10:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.11:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.11:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.12:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.12:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.13:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.13:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.14:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.14:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.15:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.15:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.16:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.16:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.17:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.17:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.18:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.18:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.19:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.19:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.2.20:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.2.20:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.4.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.4.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.4.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.4.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.8.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.8.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.8.3:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.8.3:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.8.4:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.8.4:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.10.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.10.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.10.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.10.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:0.10.3:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:0.10.3:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.0.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.0.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.1.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.1.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.2.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.2.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.3.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.3.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.4.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.4.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.5.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.5.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.5.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.5.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.5.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.5.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.6.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.6.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.6.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.6.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.6.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.6.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.7.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.7.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.8.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.8.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.8.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.8.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.9.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.9.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.9.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.9.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.9.2:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.9.2:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.9.3:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.9.3:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.10.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.10.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.11.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.11.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.12.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.12.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.13.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.13.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.14.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.14.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.15.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.15.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.15.1:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.15.1:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.16.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.16.0:*:*:*:*:*:*:*
  • cpe:2.3:a:getdbt:dbt_mcp_server:1.17.0:*:*:*:*:*:*:*
    cpe:2.3:a:getdbt:dbt_mcp_server:1.17.0:*:*:*:*:*:*:*

Protect Your Infrastructure against CVE-2026-44970: Combat Critical CVE Threats

Stay updated with real-time CVE vulnerabilities and take action to secure your systems. Enhance your cybersecurity posture with the latest threat intelligence and mitigation techniques. Develop the skills necessary to defend against CVEs and secure critical infrastructures. Join the top cybersecurity professionals safeguarding today's infrastructures.

Other 5 Recently Published CVEs Vulnerabilities

  • CVE-2026-90474 – MCPHub before 1.0.32 contains an authentication bypass vulnerability in its embedded OAuth 2.0 authorization server where client authentication is ...
  • CVE-2026-90473 – msgpack-java through 0.9.12 contains an integer overflow vulnerability in MessageUnpacker.skipValue() when processing MAP32 containers with large e...
  • CVE-2026-90472 – msgpack-java through 0.9.12 contains a stack overflow vulnerability in MessageUnpacker.unpackValue() that recursively deserializes arrays and maps ...
  • CVE-2026-89172 – Improper protection of physical side channels vulnerability in Microchip AN1044, Microchip AN953, and Microchip SW300052. This issue affects AN104...
  • CVE-2026-85200 – The GEO my WP plugin for WordPress is vulnerable to Local File Inclusion in all versions up to, and including, 4.5.5.3 via the gmw_posts_locator_aj...