Live › vulnerability › CVE-2026-84317
Go to dashboardThe Nginx UI MCP tool nginx_config_add writes caller-supplied content to nginx config without the directive validation the other config paths enforce. An authenticated MCP caller, or an agent steered by prompt injection, can add blocked directives such as js_* or perl_* and get code execution in nginx.
Summary written from the sources below. Check the originals before acting.
First seen by InfraStack 2026-10-23 19:13 UTC, 0h before NVD. All times on this page are UTC.
| Product | Ecosystem | Affected | Fixed in |
|---|---|---|---|
| github.com/0xJacky/Nginx-UI | go | < 1.9.10-0.20260703131214-23d1934099b0 | 1.9.10-0.20260703131214-23d1934099b0 |
2.4.1 and whether the MCP server is enablednginx -V or the load_module lines in the configUpgrade Nginx UI to 2.4.1, per the description. govuln lists the Go module fixed version as 1.9.10-0.20260703131214-23d1934099b0.
Each row is the first time that source carried this signal. The analyst’s rows are its own findings.
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, internal/config/validation.go (ValidateConfigFile) is a security control that blocks dangerous nginx directives — js_, perl_, load_module of the njs/perl modules, and user root. It is enforced on three of the four config-write paths: api/config/add.go, api/config/modify.go, and mcp/config/config_modify.go. The fourth path — the MCP tool nginx_config_add (mcp/config/config_add.go) — does NOT call it: it writes the caller-supplied content straight to disk and reloads nginx. An authenticated MCP caller (or an MCP agent induced via prompt injection) can therefore inject exactly the directives the control is meant to block, leading to nginx code execution on deployments where the njs/perl module is available (e.g. the official Docker image). This issue is fixed in version 2.4.1.
This page as .md · .json · in your agent: get_signal("CVE-2026-84317")
Go Vulnerability Database, CC-BY 4.0 · EPSS scores by FIRST, used with attribution · NVD data is provided by NIST and is public domain. Posts quoted belong to their authors.