# CVE-2026-54061: Dgraph Alpha group stores can be replaced via unauthenticated external snapshot import

> Unauthenticated attackers can replace Dgraph Alpha group stores via external snapshot import, leading to data loss and potential privilege escalation.

- **Severity:** Critical 9.1 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 8 Jul 2026
- **Updated:** 8 Jul 2026
- **Also known as:** GHSA-rrwh-6jrq-wp5v, GO-2026-6261

## What is CVE-2026-54061?

CVE-2026-54061 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 8 Jul 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 version 25.3.5, Dgraph Alpha exposes the RPCs used for external snapshot import on the public gRPC port `:9080` without authentication or authorization. As a result, an unauthenticated network client can open `StreamExtSnapshot` and send Badger stream data to the target group’s store. In addition, the receiver calls `Prepare()` before processing the stream. This operation deletes and replaces the existing DB data. Version 25.3.5 patches the issue.

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

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

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


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

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

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

## Is CVE-2026-54061 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54061 exists.

## Fix prompt for AI coding agents

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

What it is: CVE-2026-54061 is a critical missing authorization vulnerability in dgraph-io dgraph, published on 8 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-54061 exists.

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

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-54061/ (Markdown: https://insights.sbomify.com/CVE-2026-54061/index.md)
```

## Sources

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

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