CVE 9.1 CRITICAL

Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in NQuad Lang Field_CVE-2026-41328

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

Description

Dgraph is an open source distributed GraphQL database. Prior to 25.3.3, a vulnerability has been found in Dgraph that gives an unauthenticated attacker full read access to every piece of data in the database. This affects Dgraph's default configuration where ACL is not enabled. The attack requires two HTTP POSTs to port 8080. The first sets up a schema predicate with @unique @index(exact) @lang via /alter (also unauthenticated in default config). The second sends a crafted JSON mutation to /mutate?commitNow=true where a JSON key contains the predicate name followed by @ and a DQL injection payload in the language tag position. The injection exploits the addQueryIfUnique function in edgraph/server.go, which constructs DQL queries using fmt.Sprintf with unsanitized predicateName that includes the raw pred.Lang value. The Lang field is extracted from JSON mutation keys by x.PredicateLang(), which splits on @, and is never validated by any function in the codebase. The attacker injects a closing parenthesis to escape the eq() function, adds an arbitrary named query block, and uses a # comment to neutralize trailing template syntax. The injected query executes server-side and its results are returned in the HTTP response. This vulnerability is fixed in 25.3.3.

AI Analysis

Pre-auth full database exfiltration via DQL injection in NQuad Lang Field

Basic Information

ID CVE-2026-41328
Source GitHub_M
Published Apr 24, 2026 at 18:25
Modified Apr 24, 2026 at 19:57

Affected Product

Vendor dgraph-io
Product dgraph
Version < 25.3.3
Affected Versions dgraph-io dgraph < 25.3.3

CWE Classification

AI Assessment

AI Score 9.1 / 10
AI Severity Critical
Vendor Dgraph
Product Dgraph
Version < 25.3.3

References

💭 Join the Security Discussion

🔒 Your email address will not be published. Required fields are marked *

⚠️ Please be respectful and constructive in your comments. Security discussions should remain professional.