# CVE-2026-102748: Dgraph: Zero Unauthenticated HTTP Admin removeNode Denial of Service

> Unauthenticated attackers can disrupt the Dgraph Zero control plane and read topology data if the administrative interface is enabled.

- **Severity:** Critical 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`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 14 Oct 2026
- **Updated:** 15 Oct 2026
- **Also known as:** GHSA-qj98-gp63-54xj

## What is CVE-2026-102748?

CVE-2026-102748 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Dgraph is an open source distributed GraphQL database. Prior to 25.4.0, Dgraph Zero registers administrative HTTP routes on port 6080 without authentication when the administrative interface is enabled. The /removeNode route accepts attacker-controlled id and group values and passes them to Server.RemoveNode, where group 0 can trigger ProposePeerRemoval. A remote unauthenticated attacker who can reach the Zero HTTP port can read topology through /state, allocate identifiers through /assign, access the exposed /moveTablet administrative route, or remove membership through /removeNode, disrupting the Zero control plane and destabilizing Alpha nodes that depend on Zero. The route registration occurs in dgraph/cmd/zero/run.go, and the demonstrated membership-removal path reaches Server.RemoveNode and ProposePeerRemoval. This issue is fixed in version 25.4.0.

Weakness: CWE-862 (Missing Authorization), CWE-306 (Missing Authentication for Critical Functionality)

## Which versions are affected by CVE-2026-102748?

2 open source packages ship an affected version, including github.com/dgraph-io/dgraph/v25.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.4.0 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.4.0 |

## How do I fix CVE-2026-102748?

Upgrade github.com/dgraph-io/dgraph/v25 to 25.4.0 or later.

## Is CVE-2026-102748 being exploited?

There is no known exploitation of CVE-2026-102748 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-102748 and fix it if it is affected.

What it is: CVE-2026-102748 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 14 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-102748 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.4.0
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.4.0

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-102748/ (Markdown: https://insights.sbomify.com/CVE-2026-102748/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-102748
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-102748
- OSV: https://osv.dev/vulnerability/CVE-2026-102748

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-102748/
Summaries are generated and may contain mistakes; the official description above is the record.