CVE-2026-41328
Dgraph ≤ 25.3.3
Raw vector
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:NSummary
CVE-2026-41328 is a critical-severity Improper Neutralization of Special Elements in Data Query Logic (CWE-943) vulnerability in Dgraph Dgraph. Its CVSS base score is 9.1 (Critical).
Operationally, exploitation aligns with the MITRE ATT&CK technique Exploit Public-Facing Application (T1190); ranked at the 34th percentile by exploit likelihood (below the median); it is not currently listed in the CISA KEV catalog; a public proof-of-concept is referenced.
The strongest mitigations our analysis identified map to SI-10 (Information Input Validation) — see the control section below for these in your framework.
Deeper analysis AI-assisted summary
Synthesised by an AI model from the NVD description and linked references — a reading aid, not an authoritative source.
CVE-2026-41328 affects Dgraph, an open source distributed GraphQL database, in versions prior to 25.3.3. The vulnerability enables an unauthenticated attacker to gain full read access to every piece of data in the database when using the default configuration without ACL enabled. It arises from a DQL injection flaw in the addQueryIfUnique function within edgraph/server.go, where the function constructs DQL queries using fmt.Sprintf with an unsanitized predicateName that incorporates the raw pred.Lang value. This Lang field is parsed from JSON mutation keys via x.PredicateLang(), which splits on @ without any validation.
An unauthenticated attacker with network access to port 8080 can exploit this via two HTTP POST requests. The first targets /alter to create a schema predicate with @unique @index(exact) @lang, also unauthenticated in the default config. The second sends a crafted JSON mutation to /mutate?commitNow=true, where a JSON key embeds the predicate name followed by @ and an injection payload in the language tag position. The payload escapes the eq() function with a closing parenthesis, injects an arbitrary named query block, and uses a # comment to neutralize trailing template syntax, executing the query server-side and returning results in the HTTP response. The CVSS score is 9.1 (CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N), linked to CWE-943.
The vulnerability is fixed in Dgraph version 25.3.3. Additional details on the issue and mitigation are available in the security advisory at https://github.com/dgraph-io/dgraph/security/advisories/GHSA-x92x-px7w-4gx4.
EU & UK References
- 🇪🇺 ENISA EUVD: EUVD-2026-25595
Vulnerability Data
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…
more
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.
- CWE(s)
Related Threats
MITRE ATT&CK Enterprise Techniques
CVEs Like This One
Affected Assets
Mitigating Controls
Mitigating Controls (NIST 800-53 r5) AI
Input validation directly stops unneutralized special elements from reaching query logic.
Mitigating Controls (NIST CSF 2.0) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→CSF cross-walk (authority under review) — links open the control.
Secure SDLC practices directly require parameterized queries and input neutralization to prevent query-logic injection.
Mitigating Controls (ISO/IEC 27001:2022 Annex A) AI
Derived directly from the weakness types (CWEs) cited in the NVD entry via our AI-authored CWE→ISO cross-walk (authority under review) — links open the control.
Security testing in development catches injection vulnerabilities before release but does not itself implement the fix.
Secure development life cycle mandates input validation and query parameterization that directly prevent injection flaws.
Application security requirements explicitly call for controls against injection and improper query construction.
Secure architecture principles reduce the likelihood of query-logic flaws but do not prescribe the specific coding practice.
Secure coding standards require proper neutralization of special elements in all data queries.
Outsourced development agreements can require secure coding practices, indirectly mitigating the weakness.