Dgraph: Unauthenticated pprof endpoint leaks admin auth token
dgraph-io dgraph
Affected versions
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dgraph-io/dgraph/v25 Go |
|
|
| github.com/dgraph-io/dgraph/v24 Go |
| No fix yet |
| github.com/dgraph-io/dgraph Go |
|
dgraph-io dgraph
| Product | Affected | Fixed in |
|---|---|---|
| github.com/dgraph-io/dgraph/v25 Go |
|
|
| github.com/dgraph-io/dgraph/v24 Go |
| No fix yet |
| github.com/dgraph-io/dgraph Go |
|
all versions| No fix yet |
| github.com/hypermodeinc/dgraph/v24 Go |
|
|
Dgraph is an open source distributed GraphQL database. Versions 25.3.1 and prior contain an unauthenticated credential disclosure vulnerability where the /debug/pprof/cmdline endpoint is registered on the default mux and reachable without authentication, exposing the full process command line including the admin token configured via the --security "token=..." startup flag. An attacker can retrieve the leaked token and reuse it in the X-Dgraph-AuthToken header to gain unauthorized access to admin-only endpoints such as /admin/config/cache_mb, bypassing the adminAuthHandler token validation. This enables unauthorized privileged administrative access including configuration changes and operational control actions in any deployment where the Alpha HTTP port is reachable by untrusted parties. This issue has been fixed in version 25.3.2.
From the CVE record · GitHub_M
Dgraph exposes its process command line, including an admin token supplied through the --security startup flag, at an unauthenticated debug endpoint. If the Alpha HTTP port is reachable by untrusted parties, an attacker can retrieve the token and use it to access admin-only endpoints and change configuration. No authentication or user interaction is required to retrieve the token.
Teams running Dgraph should check Go packages github.com/dgraph-io/dgraph/v25 below 25.3.2, github.com/hypermodeinc/dgraph/v24 below 24.1.9, github.com/dgraph-io/dgraph/v24 through 24.1.7, and github.com/dgraph-io/dgraph through 1.2.8.