Improper Neutralization of Special Elements in Data Query Logic Affecting dgraph package, versions <25.3.3-r0
Threat Intelligence
The probability is the direct output of the EPSS model, and conveys an overall sense of the threat of exploitation in the wild. The percentile measures the EPSS probability relative to all known EPSS scores. Note: This data is updated daily, relying on the latest available EPSS model version. Check out the EPSS documentation for more details.
Do your applications use this vulnerable package?
In a few clicks we can analyze your entire application and see what components are vulnerable in your application, and suggest you quick fixes.
Test your applicationsSnyk Learn
Learn about Improper Neutralization of Special Elements in Data Query Logic vulnerabilities in an interactive lesson.
Start learning- Snyk IDSNYK-WOLFILATEST-DGRAPH-16570132
- published9 May 2026
- disclosed24 Apr 2026
Introduced: 24 Apr 2026
NewCVE-2026-41327 (opens in a new tab)How to fix?
Upgrade Wolfi dgraph to version 25.3.3-r0 or higher.
NVD Description
Note: Versions mentioned in the description apply only to the upstream dgraph package and not the dgraph package as distributed by Wolfi.
See How to fix? for Wolfi relevant fixed versions and status.
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 is a single HTTP POST to /mutate?commitNow=true containing a crafted cond field in an upsert mutation. The cond value is concatenated directly into a DQL query string via strings.Builder.WriteString after only a cosmetic strings.Replace transformation. No escaping, parameterization, or structural validation is applied. An attacker injects an additional DQL query block into the cond string, which the DQL parser accepts as a syntactically valid named query block. The injected query executes server-side and its results are returned in the HTTP response. This vulnerability is fixed in 25.3.3.