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

> Unauthenticated attackers can exfiltrate all database data via DQL injection in the NQuad Lang field when ACL is disabled.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 24 Apr 2026
- **Updated:** 24 Apr 2026
- **Also known as:** GHSA-x92x-px7w-4gx4, GO-2026-5749

## What is CVE-2026-41328?

CVE-2026-41328 is a critical code injection vulnerability in dgraph-io dgraph, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-943 (Improper Neutralization of Special Elements in Data Query Logic)

## Which versions are affected by CVE-2026-41328?

9 open source packages ship an affected version, including github.com/dgraph-io/dgraph, github.com/dgraph-io/dgraph/v24 and github.com/dgraph-io/dgraph/v25. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dgraph-io/dgraph` | Go | All versions | None |
| `github.com/dgraph-io/dgraph` | Go | All versions to 1.2.8 | None |
| `github.com/dgraph-io/dgraph` | Go | All versions to 1.2.8 | None |
| `github.com/dgraph-io/dgraph/v24` | Go | All versions to 24.1.8 | None |
| `github.com/dgraph-io/dgraph/v24` | Go | All versions to 24.1.8 | None |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.3 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.3 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.3 |
| `github.com/hypermodeinc/dgraph/v24` | Go | All versions | 24.1.9 |

Products: Dgraph Dgraph.

## How do I fix CVE-2026-41328?

Upgrade to a fixed version.

## Is CVE-2026-41328 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41328 exists.

## Other vulnerabilities in dgraph-io dgraph

- [CVE-2026-34976](https://insights.sbomify.com/CVE-2026-34976/): Dgraph Affected by Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization (critical 10.0)
- [CVE-2026-41492](https://insights.sbomify.com/CVE-2026-41492/): Unauthenticated Admin Token Disclosure Leading to Authentication Bypass via /debug/vars in Dgraph (critical 9.8)
- [CVE-2026-40173](https://insights.sbomify.com/CVE-2026-40173/): Dgraph: Unauthenticated pprof endpoint leaks admin auth token (critical 9.4)
- [CVE-2026-41327](https://insights.sbomify.com/CVE-2026-41327/): Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in Upsert Condition Field (critical 9.1)
- [CVE-2023-31135](https://insights.sbomify.com/CVE-2023-31135/): Dgraph Audit Log Encryption nonce reuse (low 3.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-41328 and fix it if it is affected.

What it is: CVE-2026-41328 is a critical code injection vulnerability in dgraph-io dgraph, published on 24 Apr 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-41328 exists.

Affected packages and fixed versions:
- github.com/dgraph-io/dgraph (Go): affected all versions; no fix listed
- github.com/dgraph-io/dgraph (Go): affected all versions up to 1.2.8; no fix listed
- github.com/dgraph-io/dgraph (Go): affected all versions up to 1.2.8; no fix listed
- github.com/dgraph-io/dgraph/v24 (Go): affected all versions up to 24.1.8; no fix listed
- github.com/dgraph-io/dgraph/v24 (Go): affected all versions up to 24.1.8; no fix listed
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.3
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.3
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.3
- github.com/hypermodeinc/dgraph/v24 (Go): affected all versions; fixed in 24.1.9

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-41328/ (Markdown: https://insights.sbomify.com/CVE-2026-41328/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-41328
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-41328
- OSV: https://osv.dev/vulnerability/CVE-2026-41328

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-41328/
Summaries are generated and may contain mistakes; the official description above is the record.