Dgraph: Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

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

EPSS

• CVE-2026-34976: 2.07% estimated exploitation activity in the next 30 days; percentile 81.41 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

The restoreTenant admin mutation is missing from the authorization middleware config (admin.go:499-522), 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. Authentication Bypass Every admin mutation has middleware configured in adminMutationMWConfig (admin.go:499-522) EXCEPT restoreTenant. The restore mutation has gogMutMWs (Guardian of Galaxy auth + IP whitelist + logging). restoreTenant is absent from the map. When middleware is looked up at resolve/resolver.go:431, the map returns nil. The Then() method at resolve/middlewares.go:98 checks len(mws) == 0 and returns the…

Published by the source

11 Aug 2026, 20:19 UTC

Last modified by the source

11 Aug 2026, 20:45 UTC

Source last checked

26 Oct 2026, 15:19 UTC

1. Revision 2 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-p5rh-vmhp-gvcw

2. Revision 1 · created · 24 Oct 2026

   Published from osv record GO-2026-5529

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-34976

Advisory: Dgraph: Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization
IDs: CVE-2026-34976, GHSA-p5rh-vmhp-gvcw
Record: https://patchnext.com/advisories/cve-2026-34976 (revision 2, source checked 26 Oct 2026, 15:19 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Critical (CVSS 10.0)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Partial vendor fix; fixed versions by package: github.com/dgraph-io/dgraph/v25 25.3.1; github.com/hypermodeinc/dgraph/v24 24.1.6. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/dgraph-io/dgraph/v25: affected <= 25.3.0; fixed in 25.3.1
- Go github.com/dgraph-io/dgraph: affected <= 1.2.8
- Go github.com/dgraph-io/dgraph/v24: affected <= 24.0.5
- Go github.com/hypermodeinc/dgraph/v24: affected >= 24.0.0, < 24.1.6; fixed in 24.1.6

## Suggested inspection (read-only)
- Go github.com/dgraph-io/dgraph/v25: check the installed version with your package manager.
- Go github.com/dgraph-io/dgraph: check the installed version with your package manager.
- Go github.com/dgraph-io/dgraph/v24: check the installed version with your package manager.
- Go github.com/hypermodeinc/dgraph/v24: check the installed version with your package manager.

## Supported action
No complete vendor fix is recorded. Follow the primary source's mitigation guidance and check this record again before closing anything.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/dgraph-io/dgraph/v25, github.com/dgraph-io/dgraph, github.com/dgraph-io/dgraph/v24, github.com/hypermodeinc/dgraph/v24.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-5529 (OSV record GO-2026-5529 lists affected ranges: Go github.com/dgraph-io/dgraph >=0; Go github.com/dgraph-io/dgraph/v25 >=0 =24.0.0 <24.1.6 (fixed))
- Verified: https://github.com/advisories/GHSA-p5rh-vmhp-gvcw (GitHub-reviewed advisory GHSA-p5rh-vmhp-gvcw lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 =0 =0 <=1.2.8)

Commands are suggestions: review each one before running it.