Dgraph: Zero Unauthenticated HTTP Admin removeNode Denial of Service
CVE-2026-102748GHSA-qj98-gp63-54xj
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/dgraph-io/dgraph/v25 25.4.0), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/dgraph-io/dgraph/v25
- Affected
- <= 25.3.8
- Fixed in
- 25.4.0
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-qj98-gp63-54xj lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 <25.4.0 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-qj98-gp63-54xj lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 <=25.3.8
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS 4.0
- 9.2 · CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:N/VI:H/VA:H/SC:N/SI:N/SA:H · score source
- EPSS
- CVE-2026-102748: 0.61% estimated exploitation activity in the next 30 days; percentile 49.51 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Dgraph v25.3.8 exposes a Zero HTTP administrative surface that is unauthenticated when port 6080 is reachable. The exposed routes include: - /state - /assign - /removeNode - /moveTablet An unauthenticated request to /removeNode?id=1&group=0 on a single-node standalone deployment breaks the Zero control plane and leaves Alpha repeatedly failing to reconnect to localhost:5080. Details The issue exists because Zero administrative HTTP endpoints are registered directly without any authentication or IP-whitelist wrapper. Relevant code paths: - worker/serverstate.go:41 - dgraph/cmd/zero/run.go:295-301 - dgraph/cmd/zero/http.go:106-129 - dgraph/cmd/zero/zero.go:475-477 The relevant behavior is: - disable-admin-http=false by default - /removeNode accepts attacker-controlled id and group - removeNode forwards those directly into Server.RemoveNode - for group=0, Server.RemoveNode immediately calls ProposePeerRemoval This means a remote unauthenticated caller can directly trigger…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-qj98-gp63-54xj
- Revision 2 · amended ·
Reviewed OSV alias/range/CVSS4 correction; package source scopes and original publication preserved. No customer finding resolved.
- Revision 1 · created ·
Published from osv record GHSA-qj98-gp63-54xj
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-102748 Advisory: Dgraph: Zero Unauthenticated HTTP Admin removeNode Denial of Service IDs: CVE-2026-102748, GHSA-qj98-gp63-54xj Record: https://patchnext.com/advisories/cve-2026-102748 (revision 3, source checked 26 Oct 2026, 15:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Critical (CVSS 9.2) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/dgraph-io/dgraph/v25 25.4.0. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/dgraph-io/dgraph/v25: affected <= 25.3.8; fixed in 25.4.0 ## Suggested inspection (read-only) - Go github.com/dgraph-io/dgraph/v25: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/dgraph-io/dgraph/v25. - 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/GHSA-qj98-gp63-54xj (OSV record GHSA-qj98-gp63-54xj lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 <25.4.0 (fixed)) - Verified: https://github.com/advisories/GHSA-qj98-gp63-54xj (GitHub-reviewed advisory GHSA-qj98-gp63-54xj lists affected ranges: Go github.com/dgraph-io/dgraph/v25 >=0 <=25.3.8) Commands are suggestions: review each one before running it.
Loading voting…