dbcve.org
DgraphApplication

CVE-2026-34976

CRITICAL · 10.0 CVSS v3.1 Published 2026-04-06
Fix available
A fix is available. Upgrade to after 25.3.0 or later.
See remediation →
100/100
Remediation priority · Urgent
Public exploit Remotely reachable No privileges Zero-click

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

The restoreTenant admin mutation in Dgraph before version 25.3.1 is missing from the authorization middleware configuration in admin.go, rendering it completely unauthenticated. This mutation accepts attacker-controlled parameters including backup source URLs (file:// for local filesystem, S3/MinIO), encryption key file paths, and Vault credential file paths. An unauthenticated attacker can exploit this to overwrite the entire database, read server-side files via file:// URLs, and perform SSRF attacks.

MitigationUpgrade to Dgraph 25.3.1 or later which includes the restoreTenant mutation in the authorization middleware. As a temporary mitigation, restrict network access to the admin endpoint.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.

NVD · CPE data
DgraphApplication
Affected:<= 25.3.0

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Changed
Confidentiality
High
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Check Dgraph version
    Run 'dgraph --version' or inspect the Dgraph binary metadata to determine the installed version number
    Affected if The version is 25.3.0 or earlier (< 25.3.1)
  2. Verify admin API exposure
    Determine if the Dgraph admin port (default 6080) or GraphQL admin endpoint is accessible from the network or untrusted clients
    Affected if Admin API is exposed to untrusted networks or the internet without network-level restrictions
  3. Inspect admin.go for restoreTenant authorization
    Examine the Dgraph source code or binary for admin.go and verify whether the restoreTenant mutation is included in the authorization middleware configuration
    Affected if The restoreTenant mutation is NOT present in the authorization middleware list in admin.go (indicating it remains unauthenticated)
  4. Test restoreTenant mutation accessibility
    Send an unauthenticated GraphQL or HTTP request to the restoreTenant admin mutation endpoint and observe if it accepts the request without authentication
    Affected if The mutation accepts requests without requiring valid authentication credentials

You are affected if Dgraph version is 25.3.0 or earlier AND the restoreTenant admin mutation is exposed without authentication controls at the network or application layer.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Upgrade available Upgrade to a release after 25.3.0
Interim mitigation

Upgrade to Dgraph 25.3.1 or later which includes the restoreTenant mutation in the authorization middleware. As a temporary mitigation, restrict network access to the admin endpoint.

Recommended fix High confidence

25.3.1

  1. 1. Back up all current data and configuration files before performing the upgrade.
  2. 2. Stop the Dgraph cluster gracefully to ensure all data is flushed to disk.
  3. 3. Upgrade Dgraph to version 25.3.1 or later by following your installation method (e.g., Docker, binary, package manager).
  4. 4. After upgrading, restart the Dgraph cluster.
  5. 5. Verify that the restoreTenant mutation now requires authentication by testing with an unauthenticated request - it should be rejected.
  6. 6. Confirm normal database operations are functioning correctly after the upgrade.
Caveat Minor database version upgrades may introduce subtle behavioral changes; test in a staging environment first

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Dgraph Scoped from the published advisory
  • Consultation2.0 h
  • Implementation4.0 h
  • Testing6.0 h
  • Review / QA3.0 h
15.0 hours of engineering $2,560
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $4,096.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-34976 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-34976 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data