dbcve.org
Missing AuthenticationWeakness · CWE-306

CVE-2026-54061

CRITICAL · 9.1 CVSS v3.1 Published 2026-07-08
Mitigation only
No fix yet — a mitigation exists. There is no fixed release. A documented workaround reduces exposure in the meantime.
See remediation →
100/100
Remediation priority · Urgent
Remotely reachable No privileges Zero-click 6 weeks old

Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.

NVD · unedited
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.

Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.

dbcve analysis · high confidence

Dgraph Alpha exposes snapshot import RPCs (StreamExtSnapshot) on the public gRPC port :9080 without authentication or authorization. This allows unauthenticated remote attackers to send malicious Badger stream data that triggers the Prepare() operation, which deletes and replaces all existing database data.

MitigationUpgrade to Dgraph version 25.3.5 or later to apply the patch; alternatively, implement network-level access controls to restrict port 9080 to trusted sources only.

Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.

CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.

From the vector
Attack vector
Network
Complexity
Low
Privileges
None
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
High
Availability
High

CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:H

Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.

dbcve checks

Work through these to decide whether this CVE applies to you.

  1. Identify if Dgraph Alpha is running
    Check for processes listening on gRPC port 9080 or look for dgraph alpha processes using system process listing tools
    Affected if Dgraph Alpha is running and serving on port 9080
  2. Determine installed Dgraph version
    Use the Dgraph admin endpoint or command-line tool to query the server version (e.g., dgraph version command or HTTP admin port query)
    Affected if Version is below 25.3.5 (the patched release)
  3. Verify port 9080 exposure
    Check network configuration or firewall rules to determine if port 9080 is listening on a public or untrusted network interface versus localhost only
    Affected if Port 9080 is accessible from untrusted/network-facing IP addresses
  4. Test StreamExtSnapshot RPC accessibility
    Send a gRPC request to the StreamExtSnapshot method on port 9080 without providing authentication credentials
    Affected if The RPC responds to unauthenticated requests or accepts stream initiation without auth
  5. Confirm data deletion capability
    Observe whether the Prepare() operation can be triggered via the exposed RPC, which would result in database data replacement
    Affected if The StreamExtSnapshot RPC accepts malicious Badger stream data that triggers Prepare()

A user is affected if Dgraph Alpha versions below 25.3.5 are running with gRPC port 9080 exposed to untrusted networks, allowing unauthenticated access to the StreamExtSnapshot RPC that can trigger data deletion via Prepare().

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.

dbcve · scoped
Mitigation available No clean upgrade yet — mitigate in the meantime
Mitigation

Upgrade to Dgraph version 25.3.5 or later to apply the patch; alternatively, implement network-level access controls to restrict port 9080 to trusted sources only.

Recommended fix High confidence

Dgraph version 25.3.5 or later

  1. 1. Identify all Dgraph Alpha nodes running in the deployment by checking the cluster configuration or running processes
  2. 2. Stop the Dgraph Alpha service on each node gracefully (e.g., using systemctl stop dgraph-alpha or kill signal)
  3. 3. Upgrade Dgraph to version 25.3.5 or later by updating the installation (e.g., download the new binary, update container image, or use package manager)
  4. 4. Restart the Dgraph Alpha service on each node
  5. 5. Verify the gRPC port 9080 is now properly secured with authentication enabled
  6. 6. Confirm the cluster is operational and data integrity is intact
Caveat Review Dgraph 25.3.5 release notes for any breaking changes or migration requirements before upgrading production clusters

Generated from the published advisory — verify against the referenced sources before acting.

Have this fixed Scoped from the published advisory
  • Consultation6.0 h
  • Implementation12.0 h
  • Testing6.0 h
  • Review / QA3.0 h
27.0 hours of engineering $4,800
Get help mitigating

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $7,680.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-54061 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-54061 in production — separate from our analysis above.

No notes yet

Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.

What this is

A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.

What belongs here
  • Verified mitigations, workarounds, and config changes
  • Version or environment caveats, and links to real fixes
  • No weaponised exploit code, or anything meant to cause harm
  • No spam, self-promotion, credentials, or personal data