# CVE-2026-40173: Dgraph: Unauthenticated pprof endpoint leaks admin auth token

> Unauthenticated access to the pprof endpoint leaks the admin token, allowing attackers to gain unauthorized administrative control over the Dgraph database.

- **Severity:** Critical 9.4 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Apr 2026
- **Updated:** 16 Apr 2026
- **Also known as:** GHSA-95mq-xwj4-r47p, GO-2026-5274

## What is CVE-2026-40173?

CVE-2026-40173 is a critical vulnerability in dgraph-io dgraph, published on 15 Apr 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. 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.

Weakness: CWE-522 (Insufficiently Protected Credentials), CWE-215 (Insertion of Sensitive Information Into Debugging Code), CWE-200 (Exposure of Sensitive Information to an Unauthorized Actor)

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

9 open source packages ship an affected version, including github.com/dgraph-io/dgraph, github.com/dgraph-io/dgraph/v24 and github.com/dgraph-io/dgraph/v25. It affects 1 product.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `github.com/dgraph-io/dgraph` | Go | All versions | None |
| `github.com/dgraph-io/dgraph` | Go | All versions to 1.2.8 | None |
| `github.com/dgraph-io/dgraph` | Go | All versions to 1.2.8 | None |
| `github.com/dgraph-io/dgraph/v24` | Go | All versions to 24.1.7 | None |
| `github.com/dgraph-io/dgraph/v24` | Go | All versions to 24.1.7 | None |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.2 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.2 |
| `github.com/dgraph-io/dgraph/v25` | Go | All versions | 25.3.2 |
| `github.com/hypermodeinc/dgraph/v24` | Go | All versions | 24.1.9 |

Products: Dgraph Dgraph.

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

Upgrade to a fixed version.

## Is CVE-2026-40173 being exploited?

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

## Other vulnerabilities in dgraph-io dgraph

- [CVE-2026-34976](https://insights.sbomify.com/CVE-2026-34976/): Dgraph Affected by Pre-Auth Database Overwrite + SSRF + File Read via restoreTenant Missing Authorization (critical 10.0)
- [CVE-2026-41492](https://insights.sbomify.com/CVE-2026-41492/): Unauthenticated Admin Token Disclosure Leading to Authentication Bypass via /debug/vars in Dgraph (critical 9.8)
- [CVE-2026-41327](https://insights.sbomify.com/CVE-2026-41327/): Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in Upsert Condition Field (critical 9.1)
- [CVE-2026-41328](https://insights.sbomify.com/CVE-2026-41328/): Dgraph: Pre-Auth Full Database Exfiltration via DQL Injection in NQuad Lang Field (critical 9.1)
- [CVE-2023-31135](https://insights.sbomify.com/CVE-2023-31135/): Dgraph Audit Log Encryption nonce reuse (low 3.3)

## Fix prompt for AI coding agents

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

What it is: CVE-2026-40173 is a critical vulnerability in dgraph-io dgraph, published on 15 Apr 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-40173 exists.

Affected packages and fixed versions:
- github.com/dgraph-io/dgraph (Go): affected all versions; no fix listed
- github.com/dgraph-io/dgraph (Go): affected all versions up to 1.2.8; no fix listed
- github.com/dgraph-io/dgraph (Go): affected all versions up to 1.2.8; no fix listed
- github.com/dgraph-io/dgraph/v24 (Go): affected all versions up to 24.1.7; no fix listed
- github.com/dgraph-io/dgraph/v24 (Go): affected all versions up to 24.1.7; no fix listed
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.2
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.2
- github.com/dgraph-io/dgraph/v25 (Go): affected all versions; fixed in 25.3.2
- github.com/hypermodeinc/dgraph/v24 (Go): affected all versions; fixed in 24.1.9

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

## Sources

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

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