Skip to content

AAK-MCP-NEZHA-CVE-2026-111385-001: Nezha dashboard image v2.1.0 to v2.3.14: MCP file-transfer URLs built from the Host header

Severity
MEDIUM
Category
Supply Chain (supply-chain)
Scanner
agent_audit_kit/scanners/container_image_pins.py
Auto-fixable
No.
SARIF name
NezhaMcpTransferHostHeaderInjection

What it detects

Nezha, a self-hosted server monitoring dashboard, has an MCP endpoint from v2.1.0 whose fs.download_url and fs.upload_url tools mint one-time transfer URLs from the request's Host header without validating it. Whoever controls the Host header on a victim's MCP request redirects file uploads to a host of their choice, or captures the one-time download token and replays it to read the file (CVE-2026-111385, CVSS 3.1 4.8, CWE-601, GHSA-rj3w-jrj7-x7c3). Checked in the source: cmd/dashboard/controller/mcp_transfer.go is absent at v2.0.12 and arrives in v2.1.0, where mintTransferTool takes c.Request.Host, as it still does at v2.3.14; v2.3.15 (36b742a7, "harden dashboard security boundaries") validates the host before building the URL.

How to fix

Upgrade the ghcr.io/nezhahq/nezha image to v2.3.15 or later and pin the tag. Until then, serve the dashboard behind a reverse proxy that sets the Host header itself, and do not hand transfer URLs from the MCP tools to anyone.

To confirm the finding is gone, report only this rule:

agent-audit-kit scan . --rules AAK-MCP-NEZHA-CVE-2026-111385-001

Limitations

Reads ghcr.io/nezhahq/nezha tags from v2.1.0 below v2.3.15 in compose files, Kubernetes manifests, Helm values, Dockerfiles and MCP configs. The install script writes the image untagged, and latest was the v2.3.18 digest on 2026-10-16, fixed, so an untagged reference is not reported. A dashboard installed from the release zip, which the install script also offers, is not read, even where a Dockerfile downloads it, and neither is the Go module.

References


All rules. This page is generated from the rule registry when the documentation is built; to change it, change the rule in agent_audit_kit/rules/builtin.py. To give the rule a hand-written write-up, add docs/rules/AAK-MCP-NEZHA-CVE-2026-111385-001.md: the page then shows that text, with the registry reference appended under it.