Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84317)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84317). Successful exploitation can lead to full system takeover. Exploitable via ValidateConfigFile. Mitigation: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.
Original description
The description as published by the source.
Summary
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).
Root cause — an incomplete hardening patch
Commit 3e411d38 ("Harden config write paths", 2026-04-21) introduced ValidateConfigFile and
wired it into the config-write paths — but its changeset touched only:
api/config/add.go (+6), api/config/modify.go (+8), internal/config/validation.go (+199),
mcp/config/config_modify.go (+5)
It did NOT touch mcp/config/config_add.go. So the MCP add path was left without the validation
that all of its sibling paths received. config_add.go has never called ValidateConfigFile
(verified via git history); this is an oversight in the hardening, not a regression.
Affected code (mcp/config/config_add.go, handleNginxConfigAdd)
content := mcp.GetString(ar…
Source: NIST National Vulnerability Database NVD GitHub Advisory
Auto-generated summary
Assembled by SecPulse from the source data (CVSS, CWE, affected versions) using templates — no AI involved. Check the original description and references below for exact details.
A vulnerability tracked as CVE-2026-84317 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like ValidateConfigFile over the network to misuse the product.
Successful exploitation can lead to full system takeover. CVSS score: 8.8/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-84317" on the vendor's site.
CVE-2026-84317 (github.com/0xJacky/Nginx-UI) — CWE-20 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: ValidateConfigFile / load_module / nginx_config_add / content
Patched: 1.9.10-0.20260703131214-23d1934099b0 — apply immediately
Plan: 1) Audit SBOM/dependencies, 2) Stage→prod upgrade, 3) Add WAF/proxy monitoring on affected endpoints, 4) Hunt IOCs in logs.
Refs: see the GHSA / vendor advisory / patched release linked on this page.
A vulnerability (CWE-20) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via ValidateConfigFile.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: ValidateConfigFile / load_module / nginx_config_add / content.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.9.10-0.20260703131214-23d1934099b0.
Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.
Search webserver/proxy logs for unusual request patterns matching this CVE's known IOCs. Run grep -r 'github.com/0xJacky/Nginx-UI' . against your dependency files (package-lock.json, requirements.txt, go.sum) to find affected services.
Response actions
Concrete steps and command examples for SOC/SRE teams to execute in order
-
1Identify exposure identify
grep -r 'github.com/0xJacky/Nginx-UI' . | grep -v node_modulesリポジトリと本番環境の依存ファイル (package-lock.json / requirements.txt / go.sum / Gemfile.lock 等) で
github.com/0xJacky/Nginx-UIを grep し、稼働しているサービス・バージョンを把握する。 -
2Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0ステージング環境で 1.9.10-0.20260703131214-23d1934099b0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com