# CVE-2026-34976: Dgraph Affected by Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization

> Unauthenticated attackers can overwrite the database, read server files, and perform SSRF via the restoreTenant mutation due to missing authorization checks.

- **Severity:** Critical 10.0 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 6 Apr 2026
- **Updated:** 7 Apr 2026
- **Also known as:** GHSA-p5rh-vmhp-gvcw, GO-2026-5529

## What is CVE-2026-34976?

CVE-2026-34976 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 6 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.1, the restoreTenant admin mutation is missing from the authorization middleware config (admin.go), making it completely unauthenticated. Unlike the similar restore mutation which requires Guardian-of-Galaxy authentication, restoreTenant executes with zero middleware. This mutation accepts attacker-controlled backup source URLs (including file:// for local filesystem access), S3/MinIO credentials, encryption key file paths, and Vault credential file paths. An unauthenticated attacker can overwrite the entire database, read server-side files, and perform SSRF. This vulnerability is fixed in 25.3.1.

Weakness: CWE-862 (Missing Authorization)

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

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.0.5 | None |
| `github.com/dgraph-io/dgraph/v24` | Go | All versions to 24.0.5 | None |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.1 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.1 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.1 |
| `github.com/hypermodeinc/dgraph/v24` | Go | From 24.0.0 | 24.1.6 |

Products: Dgraph Dgraph.

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

Upgrade to a fixed version.

## Is CVE-2026-34976 being exploited?

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

Public exploit code:

- Dgraph <=v25.3.0 - Admin Mutation Missing Authorization (nuclei): http/cves/2026/CVE-2026-34976.yaml

## Other vulnerabilities in dgraph-io dgraph

- [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-2026-41328](https://insights.sbomify.com/CVE-2026-41328/): Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in NQuad Lang 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-34976 and fix it if it is affected.

What it is: CVE-2026-34976 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 6 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-34976 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.0.5; no fix listed
- github.com/dgraph-io/dgraph/v24 (Go): affected all versions up to 24.0.5; no fix listed
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.1
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.1
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.1
- github.com/hypermodeinc/dgraph/v24 (Go): affected from 24.0.0; fixed in 24.1.6

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-34976/ (Markdown: https://insights.sbomify.com/CVE-2026-34976/index.md)
```

## Sources

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

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