Code Injection in github.com/0xJacky/Nginx-UI (CVE-2026-107806)
Summary
Code injection in github.com/0xJacky/Nginx-UI (CVE-2026-107806). Risk of unauthorized operations or information disclosure. Exploitable via POST /api/restore. Mitigation: upgrade to 1.9.10-0.20260728074146-a467ed652591 or later.
Original description
The description as published by the source.
Summary
An authenticated nginx-ui user can call POST /api/restore, upload a forged encrypted backup, restore app.ini, set nginx command settings such as TestConfigCmd, and then trigger command execution with POST /api/nginx/test.
This was validated on nginx-ui 2.3.11 2(523) 6c86e5a5 in the local Docker container uozi/nginx-ui:latest.
Impact
An authenticated user can overwrite nginx-ui application configuration and database state through restore, including protected settings that are normally not writable through the settings API. By setting nginx command fields in the restored app.ini, the attacker can execute commands in the nginx-ui runtime context. This affects confidentiality, integrity, and availability because the attacker can read or replace secrets, change node/JWT secrets, corrupt application state, and execute arbitrary commands.
Affected Version / Environment
- Version:
nginx-ui 2.3.11 2(523) 6c86e5a5 - Deployment: local Docker,
uozi/nginx-ui:latest - Base URL used in validation:
http://127.0.0.1:8080
Root Cause
/api/restore is reachable through normal authenticated-user authorization. The restore handler accepts attacker-supplied backup key material, validates the manifest with a key derived from that supplied AES key, decrypts attacker-controlled backup contents, and copies restored app.ini into the live nginx-ui config path.
Relevant code paths:
api/backup/router.go:POST /api/restoreapi/backup/restore.go:…
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-107806 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like POST /api/restore over the network to misuse the product.
Risk of unauthorized operations or information disclosure.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074146-a467ed652591 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-107806" on the vendor's site.
CVE-2026-107806 (github.com/0xJacky/Nginx-UI) — CWE-94
Attack surface: POST /api/restore / POST /api/nginx/test / app.ini / TestConfigCmd
Patched: 1.9.10-0.20260728074146-a467ed652591 — 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.
Arbitrary code execution (CWE-94) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via POST /api/restore.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: POST /api/restore / POST /api/nginx/test / app.ini / TestConfigCmd.
Severity: ?. Risk of unauthorized operations or information disclosure.
Update to 1.9.10-0.20260728074146-a467ed652591.
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/restore 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/restore' /var/log/nginx/access.log | grep -E '(unusual_payload|sqli_pattern)'アクセスログで
POST /api/restoreへの異常なリクエスト (不正な認証ヘッダ・SQLメタ文字)を過去 30〜90日分捜索。WAF/SIEM があれば該当パスのアラート発火履歴を確認。 -
3Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074146-a467ed652591ステージング環境で 1.9.10-0.20260728074146-a467ed652591 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 2 で見つけた異常検知の続報チェックを含めること。
-
4Post-deployment verification verify
Replay attack against POST /api/restore on staging to confirm patch closes the vectorパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 2 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
References
- advisory nvd.nist.gov
- package github.com
- web github.com
- web github.com
- web github.com
- web github.com