Vulnerability in github.com/dgraph-io/dgraph (CVE-2026-34976)

Summary

Vulnerability in github.com/dgraph-io/dgraph (CVE-2026-34976). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 25.3.1 or later.

Original description

The description as published by the source.

The restoreTenant GraphQL mutation in Dgraph was missing from the admin mutation middleware configuration. This omission bypassed all authentication, IP whitelisting, and audit logging for this mutation.

An unauthenticated remote attacker could use this mutation to trigger a database restore from an arbitrary URL, potentially leading to a complete database overwrite, Server-Side Request Forgery (SSRF), or arbitrary file read on the host system.

Source: OSV.dev (Open Source Vulnerabilities) NVD GitHub Advisory OSV

Auto-generated summary

Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.

A vulnerability tracked as CVE-2026-34976 has been found in github.com/dgraph-io/dgraph.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/dgraph-io/dgraph to 25.3.1 or later.
If unsure, ask your IT team or search "github.com/dgraph-io/dgraph CVE-2026-34976" on the vendor's site.

CVE-2026-34976 (github.com/dgraph-io/dgraph)
Patched: 25.3.1 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.

❓ What is the problem

A vulnerability (unclassified) exists in github.com/dgraph-io/dgraph.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/dgraph-io/dgraph.

🔥 Severity

Severity: ?. Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 25.3.1.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/dgraph-io/dgraph' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.

Response actions

Concrete steps and command examples for SOC/SRE teams to execute in order

1
Identify exposure identify
```
grep -r 'github.com/dgraph-io/dgraph' . | grep -v node_modules
```
リポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で github.com/dgraph-io/dgraph を grep し、稼働しているサービス・バージョンを把握する。
2
Apply patch patch
```
Upgrade github.com/dgraph-io/dgraph to 25.3.1
```
ステージング環境で 25.3.1 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
3
Post-deployment verification verify
```
Confirm patched version is live in production
```
パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

Go github.com/dgraph-io/dgraph

[{"type":"SEMVER","events":[{"introduced":"0"}]}]

Go github.com/dgraph-io/dgraph/v25

[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"25.3.1"}]}]

Go github.com/hypermodeinc/dgraph/v24

[{"type":"SEMVER","events":[{"introduced":"24.0.0"},{"fixed":"24.1.6"}]}]

References

advisory github.com
patch github.com
web github.com