HOL LogoGuard

Explore HOL

  • HOL home
  • AI agent registry
  • AI plugins
  • Open standards
  • HOL members
  • Sponsor HOL
  • Advertise with HOL

Guard product

  • Guard overviewLocal security and control for AI agents and the tools they use.
  • FeaturesRuntime protection, policy routing, review, and evidence.

Explore Guard

  • Product previewWalk through Guard surfaces in read-only demo mode.
  • ComparisonCompare Guard with native controls and AI security vendors.

AI tools

  • All AI toolsEvery supported AI tool and how Guard applies policy to it.
  • Codex
  • Claude Code
  • Cursor
  • Antigravity CLI
  • OpenCode
  • Hermes
  • OpenClaw
  • GitHub Copilot CLI
  • Antigravity
  • Kimi
  • Grok
  • Pi / Oh My Pi
  • Zcode

Extensions

  • All extensionsBrowse command and MCP coverage with owners and stated limits.
  • Command coverageShell command protection across clouds, databases, backups, and packages.
  • MCP server coverageSee how Guard maps risk state across MCP tools and servers.
  • Core safetyThe safety floor listings that ship with Guard.
  • Data and resilienceBackup and storage command protection.
  • Cloud and infrastructureAWS, Azure, GCP, Kubernetes, and more.

Security

  • AI security hubSecurity research, advisories, and agent safety coverage.
  • AI tool securitySecurity profiles for each supported coding agent.
  • Safe labsHands-on attack simulations with safe boundaries.
  • Redacted warningsReal blocked actions with sensitive details removed.
  • AdvisoriesCoordinated disclosure reports for AI tooling.
  • Active CVEsSearch active CVEs affecting AI tooling.

Learn

  • Security guidesPractical guides for securing AI agent workflows.
  • DocsInstall, configure, and operate Guard with confidence.
  • ResearchPublished security research, benchmarks, and methodology.

Community

  • ReleasesVersion history, shipped changes and upgrade notes.
  • ContributorsThe people and contributions behind HOL Guard.
  • AffiliatesShare Guard with your audience and earn from referrals.
  • SponsorFund agreed research, implementation and shared testing through the HOL Partner Program.
  • AdvertiseCompare README logo placements, previews and monthly prices, or promote a plugin or extension.
PricingEnterpriseOpen AppInstall Guard
  1. Guard
  2. Security
  3. CVEs
  4. CVE 2026 40173 dgraph unauthenticated debugpprofcmdline
HOL Guard

Public security guidance for teams protecting AI harnesses, MCP servers, skills, prompts, and local tool execution.

Install Guard

AI Security

  • Prompt injection
  • MCP security
  • OWASP MCP mapping
  • Supply chain

Resources

  • Trust packet
  • Harness setup
  • Redacted warnings
  • Safe labs

Product

  • Install Guard
  • Pricing
  • Open dashboard
Guard
  • Guard Overview
  • Releases
  • Contributors
  • Install Guard
  • Pricing
Docs
  • Documentation Index
  • Developer Hub
  • API Reference
  • Root OpenAPI
  • Registry OpenAPI
  • Run in Postman
  • Standards
  • Submit ERC-8004 Contract
  • Feature Your Agent
Best Plugins
  • Browse Plugins
  • Plugin Launches
  • Best Claude Plugins
  • Best Codex Plugins
  • Best Grok Plugins
  • Best Kimi Plugins
  • Best DeepSeek Plugins
  • Best Antigravity Plugins
  • Best MCP Servers
  • Best Cursor Plugins
  • Best OpenCode Plugins
Best Agents
  • Best ERC-8004 Agents
  • Best Virtuals Agents
  • Best MCP Servers
  • Best A2A Agents
  • Best x402 Payable
  • All Categories
Community
  • Telegram
  • X
More
  • About HOL
  • Sponsor
  • Advertise
  • Contact
  • Blog
  • GitHub
  • Privacy
  • Terms of Service
Settings

Copyright © 2026 HOL DAO LLC. All rights reserved.

Back to active CVEs
Critical · CVSS 9.4CVE-2026-40173GHSA-95MQ-XWJ4-R47P

Dgraph: Unauthenticated /debug/pprof/cmdline discloses admin auth token, enabling unauthorized access to protected Alpha admin endpointsCVE-2026-40173

Answer in brief

CVE-2026-40173 records a Critical severity (CVSS 9.4) vulnerability in Dgraph: Unauthenticated /debug/pprof/cmdline discloses admin auth token, enabling unauthorized access to protected Alpha admin endpoints. The current sources do not mark it as known exploited. The current feed maps github.com/dgraph-io/dgraph (go), github.com/dgraph-io/dgraph/v24 (go), github.com/dgraph-io/dgraph/v25 (go), github.com/hypermodeinc/dgraph/v24 (go). Check affected ranges and fixed versions before updating.

Analysis pending evidence review

HOL Guard separates source facts from reviewed analysis. See the methodology.

Published Apr 16, 2026Updated Sep 10, 2026Source checked Oct 26, 2026First seen by HOL Aug 11, 2026Material review Sep 10, 2026
Upstream Advisory

Record context

Vulnerability class
Missing Auth
EPSS
Not reported
CWE IDs
Not reported
Source
OSV
Source checked
Oct 26, 2026
References
4 linked sources
Open source record

Key facts

Risk
Critical · CVSS 9.4
Exploitation
Not marked as known exploited
Affected software
4 mapped packages or products
Fix availability
Available

Why this deserves its current priority

CVSS is 9.4. The current sources do not mark it as known exploited. Treat this as a source-backed prioritization signal, not a statement about your environment.

Analysis status

Analysis pending evidence review

Factual feed record only; HOL analysis is not approved for indexing. Read the methodology.

Affected scope and exposure questions

The current feed maps github.com/dgraph-io/dgraph (go), github.com/dgraph-io/dgraph/v24 (go), github.com/dgraph-io/dgraph/v25 (go), github.com/hypermodeinc/dgraph/v24 (go). Check affected ranges and fixed versions before updating.

Mapped affected packages and fixed versions
PackageAffected rangeFixed version
github.com/dgraph-io/dgraphgo>=0Not reported
github.com/dgraph-io/dgraph/v24go>=0Not reported
github.com/dgraph-io/dgraph/v25go>=0 <25.3.225.3.2
github.com/hypermodeinc/dgraph/v24go>=0 <24.1.924.1.9

Recommended response

  1. 1Check inventory. Check lockfiles and deployed manifests for github.com/dgraph-io/dgraph, github.com/dgraph-io/dgraph/v24, github.com/dgraph-io/dgraph/v25.
  2. 2Review the reported fix. Update github.com/dgraph-io/dgraph/v25 to 25.3.2; github.com/hypermodeinc/dgraph/v24 to 24.1.9 if you use the affected versions. Test the change in a non-production environment first.

Evidence timeline and material changes

  1. Published upstream

    Apr 16, 2026

    Evidence: source:osv:source_dates:source-dates:record
  2. Source modified

    Sep 10, 2026

    Evidence: source:osv:source_dates:source-dates:record
  3. First seen by HOL

    Aug 11, 2026

Sources and claim methodology

  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • GitHub security advisorygithub.com
  • NVD vulnerability recordnvd.nist.gov
Upstream source description

### Summary An unauthenticated debug endpoint in Dgraph Alpha exposes the full process command line, including the configured admin token from `--security "token=..."`. This does not break token validation logic directly; instead, it discloses the credential and enables unauthorized admin-level access by reusing the leaked token in `X-Dgraph-AuthToken`. ### Details The behavior occurs entirely within core Alpha HTTP routing and does not require any external proxy, plugin, or non-core integration. The core issue is not that admin token protection is absent, but that the protected secret is exposed in cleartext through an unauthenticated core debug endpoint. Relevant code paths: - `dgraph/cmd/alpha/run.go:17` imports `net/http/pprof`, which registers `/debug/pprof/*` handlers on the default mux. - `dgraph/cmd/alpha/run.go:533` uses `http.Handle("/", audit.AuditRequestHttp(baseMux))`, so default-mux handlers remain reachable. - `dgraph/cmd/alpha/admin.go:52` enforces admin token checks in `adminAuthHandler` for admin endpoints. - `dgraph/cmd/alpha/admin.go:74` shows `/admin/config/cache_mb` behind `adminAuthHandler`. Credential-exposure chain: 1. `/debug/pprof/cmdline` is reachable without authentication. 2. Its output includes the configured admin token from process arguments. 3. The disclosed token is accepted by `adminAuthHandler` when sent as `X-Dgraph-AuthToken`. 4. An attacker gains unauthorized access to admin-only functionality. Observed local evidence (safe validation): - Request: `GET /admin/config/cache_mb` without token - Status: 200 (request rejected at application layer) - Body contains error: `Invalid X-Dgraph-AuthToken` - The endpoint returns HTTP 200 but indicates authentication failure in the response body. - Request: `GET /debug/pprof/cmdline` without token - Status: 200 - Body excerpt includes: `--security=token=TopSecretToken123;` - Request: `GET /admin/config/cache_mb` with `X-Dgraph-AuthToken: TopSecretToken123` - Status: 200 - Body: `4096` Important policy/triage clarification: - This issue persists even when the admin-token security feature is enabled: the token itself is exposed via an unauthenticated core debug endpoint, making this more than a misconfiguration-only concern. - Network restrictions (bind/whitelist/firewall) may reduce exposure, but they do not remediate the underlying credential disclosure behavior. ### PoC - Branch: `main` - Commit: `b15c87e93` - Describe: `v25.3.1` Preconditions: - Alpha HTTP port is reachable by attacker traffic. - Admin token is configured via supported startup flag: `--security "token=..."`. - `/debug/pprof/*` is exposed on the same Alpha HTTP listener. - This behavior occurs with documented startup flags and without any non-default or unsupported configuration. Reproduction steps: 1. Start Zero and Alpha (example local setup): - `dgraph zero --my=127.0.0.1:5280 --port_offset=200 --bindall=false --wal=./zw` - `dgraph alpha --my=127.0.0.1:7280 --zero=127.0.0.1:5280 --port_offset=200 --bindall=false --security "token=TopSecretToken123;" --postings=./p --wal=./w --tmp=./t` 2. Verify admin endpoint rejects unauthenticated request: - `curl -i http://127.0.0.1:8280/admin/config/cache_mb` - Expected body includes `Invalid X-Dgraph-AuthToken`. 3. Read token from unauthenticated debug endpoint: - `curl -s http://127.0.0.1:8280/debug/pprof/cmdline` - Expected output includes `--security=token=TopSecretToken123;`. 4. Reuse leaked token against admin endpoint: - `curl -i -H "X-Dgraph-AuthToken: TopSecretToken123" http://127.0.0.1:8280/admin/config/cache_mb` - Expected: successful response (example observed: `4096`). Note: The PoC uses `127.0.0.1` only for safe local validation. The vulnerable condition is unauthenticated reachability of `/debug/pprof/cmdline`; in any deployment where Alpha HTTP is reachable by untrusted parties, the same token disclosure and subsequent unauthorized admin access apply. ### Impact - Unauthenticated disclosure of a sensitive admin credential via debug endpoint, enabling unauthorized privileged administrative access through token reuse - Operators running Dgraph Alpha with admin token configured, where Alpha HTTP/debug routes are reachable by untrusted users or networks. The attack requires network reachability to the Alpha HTTP port. In deployments where this interface is exposed beyond trusted boundaries, the issue is remotely exploitable without authentication. Depending on exposed admin functionality in deployment policy, this may allow configuration changes, operational control actions, and other privileged administrative operations exposed through `/admin/*`.

Quoted source text, attributed separately from HOL analysis.