Information Disclosure in github.com/0xJacky/Nginx-UI (CVE-2026-107811)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-107811). Successful exploitation can lead to full system takeover. Exploitable via POST /api/system/restart.. Mitigation: upgrade to 1.9.10-0.20260728091109-0ecbd106c37b or later.
Original description
The description as published by the source.
Summary
0xJacky/nginx-ui contains a high-severity trust-boundary failure between ordinary users and cluster node credentials. The source code shows that cluster node list and detail endpoints are reachable by ordinary authenticated users and return node objects containing the token field.
That same token is also used as the X-Node-Secret shared credential for node-to-node authentication. When the middleware receives a correct node secret, it upgrades the request to initUser and bypasses the normal user-authentication path. As a result, any low-privileged authenticated user can first read a node token from /api/nodes and then impersonate a trusted node against a remote node's management API, achieving cross-node administrative authentication bypass.
Details
The root cause is a combination of sensitive credential exposure and improper trust elevation for node-to-node authentication. First, router/routers.go:87-105 mounts cluster.InitRouter(g) inside the shared /api authenticated route group, so any successfully authenticated user can access node list and detail endpoints.
Next, api/cluster/node.go:19-48 implements GetNode and GetNodeList by directly returning analytic.GetNode(node). Meanwhile, model/node.go:8-13 defines Token with the JSON tag json:"token", meaning the node secret is serialized into API responses. The surrounding code path does not redact that field. Therefore, a low-privileged user can call /api/nodes or /api/nodes/:id and retrieve both the target node URL…
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-107811 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like POST /api/system/restart. 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.20260728091109-0ecbd106c37b or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-107811" on the vendor's site.
CVE-2026-107811 (github.com/0xJacky/Nginx-UI) — CWE-200 / CVSS v3 8.8
Attack vector: remote (network-reachable) / no user interaction
Attack surface: POST /api/system/restart. / POST /api/login / GET /api/nodes / GET /api/nodes/
Patched: 1.9.10-0.20260728091109-0ecbd106c37b — 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.
Information disclosure (CWE-200) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via POST /api/system/restart..
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: POST /api/system/restart. / POST /api/login / GET /api/nodes / GET /api/nodes/.
Severity: High (CVSS 8.8/10). Successful exploitation can lead to full system takeover.
Update to 1.9.10-0.20260728091109-0ecbd106c37b.
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/system/restart. 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/system/restart.' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/system/restart.への異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728091109-0ecbd106c37bステージング環境で 1.9.10-0.20260728091109-0ecbd106c37b に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/system/restart. on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。