CVE-2026-102748: Missing Authentication Flaw in dgraph-io dgraph Scores 9.2 on CVSS
A newly published critical vulnerability in dgraph-io dgraph carries a CVSS score of 9.2. Here is what is affected and how to respond.
Key points
- CVE-2026-102748 affects dgraph-io dgraph.
- CVSS 9.2 (Critical).
- No exploitation confirmed yet.
dgraph-io dgraph is affected by CVE-2026-102748, a missing authentication that the National Vulnerability Database rates 9.2 out of 10.
At a glance
- CVE
- CVE-2026-102748
- Product
- dgraph-io dgraph
- CVSS
- 9.2 Critical
- Weakness
- missing authentication
- Exploited
- No known exploitation
What is the vulnerability?
The NVD entry states: 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.
Affected versions
| Vendor | Product | Versions |
|---|---|---|
| Dgraph-Io | dgraph | < 25.4.0 |
Is it being exploited?
There is no public confirmation of exploitation at the time of publication. It does not appear in CISA's Known Exploited Vulnerabilities catalog. We will update this report if that changes.
What should you do?
- Identify whether the affected product and versions run in your environment.
- Apply the vendor update listed in the advisory as soon as it is available.
- Limit network exposure of the affected service until it is patched.
- Monitor the vendor advisory for updated guidance or exploitation reports.
What to do and how to stay safe: CVE-2026-102748
- Vulnerability severity scores ignore your specific architecture and context.
- Exploitability depends on network exposure and user behavior, not just code flaws.
- Prioritization requires continuous asset inventory and threat intelligence alignment.
Risk-based vulnerability management focuses your limited resources on the flaws that actually threaten your business. Start by mapping your critical assets and checking for active exploits to prioritize your backlog.
Step-by-step guide: Risk-Based Vulnerability Management: Prioritize Fixes by Actual Danger
General security guidance from the Threat Times newsroom. It is not confirmed advice from the organisations named in this story.
Frequently asked questions
What is CVE-2026-102748?
CVE-2026-102748 is a missing authentication vulnerability in dgraph-io dgraph.
How severe is CVE-2026-102748?
It has a CVSS score of 9.2 Critical.
Is CVE-2026-102748 being exploited?
There is no public confirmation of exploitation at the time of publication.
