Vulnerability in github.com/dgraph-io/dgraph/v25 (CVE-2026-102748)
Summary
Vulnerability in github.com/dgraph-io/dgraph/v25 (CVE-2026-102748). Risk of unauthorized operations or information disclosure. Exploitable via group. Mitigation: upgrade to 25.4.0 or later.
Original description
The description as published by the source.
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/server_state.go:41dgraph/cmd/zero/run.go:295-301dgraph/cmd/zero/http.go:106-129dgraph/cmd/zero/zero.go:475-477
The relevant behavior is:
disable-admin-http=falseby default/removeNodeaccepts attacker-controlledidandgroupremoveNodeforwards those directly intoServer.RemoveNode- for
group=0,Server.RemoveNodeimmediately callsProposePeerRemoval
This means a remote unauthenticated caller can directly trigger destructive membership operations if 6080 is exposed.
PoC
Read state without authentication
curl -i http://127.0.0.1:6080/state
Observed response included:
- Zero node
id=1 groupId=0leader=true- cluster topology and tablet state
Write-capable route without authentication
curl -i 'http://127.0.0.1:6080/assign?what=nsids&num=1'
Observed response:
HTTP/1.1 200 OK
...
{"startId":"…
Source: GitHub Security Advisories (Global) NVD GitHub Advisory
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-102748 has been found in github.com/dgraph-io/dgraph/v25.
Attackers can target a specific entry point like group over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/dgraph-io/dgraph/v25 to 25.4.0 or later.
If unsure, ask your IT team or search "github.com/dgraph-io/dgraph/v25 CVE-2026-102748" on the vendor's site.
CVE-2026-102748 (github.com/dgraph-io/dgraph/v25) — CWE-306
Attack surface: group / removeNode / Server.RemoveNode / ProposePeerRemoval
Patched: 25.4.0 — 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.
A vulnerability (CWE-306) exists in github.com/dgraph-io/dgraph/v25. Attackers reach the vulnerable code path via group.
Check the vendor advisory for the affected versions of github.com/dgraph-io/dgraph/v25. Attack surface: group / removeNode / Server.RemoveNode / ProposePeerRemoval.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 25.4.0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/dgraph-io/dgraph/v25' . 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
-
1Identify exposure identify
grep -r 'github.com/dgraph-io/dgraph/v25' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/dgraph-io/dgraph/v25を grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/dgraph-io/dgraph/v25 to 25.4.0ステージング環境で 25.4.0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。