External risk intelligence

MongoDB C# Driver DNS SRV Vulnerability Allows Host Spoofing

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-129938

The vulnerability exists within a database driver (MongoDB C# driver) used by applications to connect to database clusters. While the mechanism involves DNS resolution, the driver itself is a client-side component integrated into application code, not an internet-facing service or appliance. Public internet exposure is uncommon as this occurs within internal application environments.

Halo Surface Signal: 2 out of 5 — less likely to be public-facing.

External exposure likelihood

Horizon Alert

Summary of the vulnerability and why it matters

This vulnerability in the MongoDB C# driver could allow an attacker to intercept application data and credentials by manipulating DNS responses during connection string resolution. It affects how applications connect to MongoDB databases, potentially exposing sensitive information.

  • Driver flaw can expose application data.
  • Affects how applications connect to MongoDB.
  • Confirm driver relevance to your applications.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker who can respond to a client's DNS SRV query can trick the MongoDB C# driver into connecting to a malicious host. This happens when the driver resolves a connection string, potentially leading to sensitive application data, credentials, and query results being sent to the attacker-controlled host, or to forged query results being returned.

  • Unauthenticated network access required.
  • DNS SRV query response.
  • Data disclosure and forged query results.

Live Threat

Current exploitation, exposure, and threat context

An unauthenticated party able to answer DNS SRV queries could manipulate a client application's server list by introducing a host outside the trusted domain. When the application uses the affected API to resolve a connection string, its data, authentication credentials, and query results could be sent through this untrusted host, potentially leading to unintended data disclosure and forged query results.

  • Application data and credentials.
  • DNS SRV query responses.
  • Unintended data disclosure.

Operational Fix

Recommended remediation, mitigation, and detection steps

This vulnerability impacts applications using the MongoDB C# driver that resolve connection strings via DNS SRV queries. Technical leaders should prioritize identifying applications utilizing this driver and confirm their DNS resolution configurations. Coordinating with application owners and infrastructure teams is crucial to understand the scope of exposure and plan appropriate remediation, which may involve code updates or configuration changes to mitigate the risk of data and credential disclosure.

  • Application owners should assess driver usage.
  • Verify DNS SRV resolution configurations.
  • Plan application-level code updates.

Supplementary metadata

Validate whether this threat affects your internet-facing exposure.

Halo Threat Intelligence helps prioritize remediation with Halo Surface Signal and H/A/L/O context. Start exposure validation with a free external attack surface trial.

Frequently asked questions

What is the MongoDB C# driver and how is it used?

The MongoDB C# driver is a library integrated into software applications. Developers use it to enable their C# or .NET programs to communicate with MongoDB databases. It handles the low-level work of connecting to database clusters, managing sessions, and executing queries so the application can interact with stored data.

What is the weakness in CVE-2026-129938?

This vulnerability is classified as CWE-88, which involves improper neutralization of special elements. In this specific case, the driver fails to properly validate the hostnames returned during DNS SRV resolution. Because it does not strictly enforce that these hosts belong to a trusted domain, an attacker can trick the driver into accepting an unauthorized server.

How does an attacker trigger this vulnerability?

An attacker must be positioned to intercept or respond to the application's DNS SRV queries. By providing a malicious DNS response, they can inject an untrusted host into the driver's connection list. Simply having network access is not enough; the attack relies on the application resolving a connection string via DNS at the precise moment the attacker provides the spoofed record.

Is my application at risk if it is not internet-facing?

According to Halo Surface Signal, this vulnerability is unlikely to be exposed on the public internet because the driver is a client-side component, not a standalone service. However, if an attacker has already gained a foothold within your internal network and can manipulate DNS traffic between your application and its database, the risk remains relevant.

How should I respond to CVE-2026-129938?

Begin by auditing your application inventory to identify which services utilize the MongoDB C# driver. Once identified, consult with your infrastructure and security teams to verify how your DNS SRV lookups are configured. You should prioritize planning for upcoming code updates or configuration hardening to ensure the driver validates connection targets properly.

References