External risk intelligence

Unauthenticated attackers can steal all data from Dgraph databases.

CVE advisorySeverity: CRITICAL (CVSS 9.1)

CVE-2026-41327

A flaw in the Dgraph database allows an external attacker to gain full read access to all stored information. This vulnerability creates a significant risk of exposing sensitive proprietary and customer data held within the system.

2Halo Surface Signal

Dgraph

before 25.3.3

External exposure likelihood

Halo Surface Signal score for CVE-2026-41327

Dgraph is a database, which is typically a backend service intended to be isolated behind an application layer or internal network controls. Direct exposure of its mutation endpoints to the public internet is an uncommon and non-standard deployment pattern.

Horizon Alert

Summary of the vulnerability and why it matters

This issue in Dgraph allows an unauthenticated attacker to read all data within the database. It's critical to address because it impacts the default configuration where access controls are not enabled, exposing sensitive information.

  • Gives attackers full data access.
  • Affects Dgraph's default configuration.
  • Requires only a single HTTP request.

Attack Path

How an attacker could exploit the issue

An unauthenticated attacker can exploit this flaw by sending a crafted HTTP POST request to the `/mutate` endpoint. This request bypasses authorization checks, allowing the attacker to execute arbitrary DQL queries on the database. The attacker can then exfiltrate sensitive data by injecting a malicious query block into the `cond` field of an upsert mutation.

  • No authentication required.
  • Target: Dgraph's `/mutate` endpoint.
  • Precondition: ACLs must be disabled.

Live Threat

Current exploitation, exposure, and threat context

This critical vulnerability allows unauthenticated attackers to read all data from Dgraph databases when ACLs are not enabled. The attack is straightforward, involving a crafted HTTP POST request that exploits insecure handling of user input in DQL queries. Attackers are likely to target this because of the direct data exfiltration capability and the ease of exploitation.

  • Unauthenticated data access
  • Simple HTTP POST exploit
  • Affects default configuration

Priority actions

Operational Fix

Recommended remediation, mitigation, and detection steps

Prioritize updating Dgraph to version 25.3.3 or later to address a critical vulnerability allowing unauthenticated attackers full read access to data. If immediate patching is not feasible, review your Dgraph configurations for enabled ACLs and consider network segmentation or blocking direct internet access to the affected endpoints.

  • Update Dgraph to 25.3.3.
  • Isolate services if patching is delayed.
  • Monitor for suspicious query patterns.

Frequently asked questions

What is Dgraph and what is it used for?

Dgraph is an open-source distributed GraphQL database. It's used for storing and querying data, and in its default configuration, it may not have access control lists (ACLs) enabled, which can leave it vulnerable.

What kind of weakness does CVE-2026-41327 represent in Dgraph?

CVE-2026-41327 represents a server-side injection vulnerability, specifically CWE-943. This means an attacker can inject malicious code, in this case, DQL queries, into the database's input that is then executed by the server.

How can an attacker exploit this Dgraph vulnerability?

An attacker can exploit this by sending a single HTTP POST request to the `/mutate` endpoint with a specially crafted `cond` field. This allows them to inject DQL query blocks that are executed server-side, provided that ACLs are not enabled in the Dgraph configuration.

Who needs to be concerned about this Dgraph vulnerability?

Organizations running Dgraph, especially those using its default configuration without enabled ACLs, should be concerned. This is because the vulnerability allows for full data exfiltration, and while Dgraph is typically a backend service, its exposure to the internet is a key factor in determining risk.

What is the first step to respond to this Dgraph threat?

The most important first step is to update Dgraph to version 25.3.3 or later, as this version contains the fix for the vulnerability. If immediate patching isn't possible, consider isolating the Dgraph service or blocking direct internet access to its endpoints.

References