Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84316)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84316). Successful exploitation can lead to full system takeover. Exploitable via POST /api/configs. Mitigation: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.
Original description
The description as published by the source.
Summary
config.ValidateConfigFile is the security control that blocks dangerous nginx directives
(js_*, perl_*, load_module of njs/perl modules, user root). Its directive scanner is
bypassable: it splits the config by newlines and inspects only the FIRST token of each line, but
nginx separates directives with ;, not newlines. Putting a benign directive first and the blocked
directive after a ; on the SAME line defeats every check. The include directive is also not on
the denylist. As a result, an authenticated caller can inject the exact directives the hardening was
meant to block, through EVERY path that calls the validator — POST /api/configs (add), the REST
config modify endpoint (api/config/modify.go), the MCP nginx_config_modify tool, and the
site/stream save paths (internal/site/save.go, internal/stream/save.go). On deployments where
nginx has the njs/perl module (the official uozi/nginx-ui Docker image ships ngx_http_js_module.so),
this leads to code execution in the nginx worker; with user root the workers run as root.
This is distinct from the config_add gap (the MCP nginx_config_add tool not calling the validator at
all): here the validator IS called and still bypassed, so fixing config_add does not fix this.
Root cause (internal/config/validation.go, ValidateConfigDirectives)
for _, line := range bytes.Split(content, []byte("\n")) { // splits on \n only
trimmed := strings.TrimSpace(string(line))
...
directive…
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-84316 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like POST /api/configs 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-84316" on the vendor's site.
CVE-2026-84316 (github.com/0xJacky/Nginx-UI) — CWE-20 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/configs / config.ValidateConfigFile / load_module / include
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 POST /api/configs.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: POST /api/configs / config.ValidateConfigFile / load_module / include.
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 POST /api/configs requests with malformed payloads or SQL meta-characters. 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 し、稼働しているサービス・バージョンを把握する。 -
2Hunt for indicators of compromise detect
grep 'POST /api/configs' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/configsへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0ステージング環境で 1.9.10-0.20260703131214-23d1934099b0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/configs on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- web github.com
- web github.com
- web github.com
- web nvd.nist.gov
- web github.com