Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-107805)
Summary
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-107805). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.10-0.20260901043436-8c9b9a1aff21 or later.
Original description
The description as published by the source.
Summary
In Nginx UI versions 2.5.0 through 2.5.x, the node-signature authentication path staged an attacker-controlled request body in a temporary file and synchronized it to disk before validating the body digest and cryptographic signature. An unauthenticated remote client that can reach the API can provide syntactically valid signature metadata and cause storage and I/O consumption before the request is rejected.
Impact
Concurrent malicious requests can consume temporary filesystem capacity, disk I/O, and request-processing resources, potentially disrupting Nginx UI and other services that share the filesystem. The issue affects availability only; it does not bypass authentication and does not provide confidentiality or integrity impact. Deployment-specific reverse-proxy body limits, filesystem quotas, and concurrency limits may reduce practical impact.
Remediation
Upgrade to Nginx UI 2.6.0 or later. The fix authenticates signed request metadata before staging the body and enforces an application-level streaming size limit with cleanup for rejected requests.
Fix commit: https://github.com/0xJacky/nginx-ui/commit/8c9b9a1aff218ee6c980d047b750e49da3c46796
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-107805 has been found in github.com/0xJacky/Nginx-UI.
Risk of unauthorized operations or information disclosure. CVSS score: 7.5/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260901043436-8c9b9a1aff21 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-107805" on the vendor's site.
CVE-2026-107805 (github.com/0xJacky/Nginx-UI) — CWE-400 / CVSS v3 7.5
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.9.10-0.20260901043436-8c9b9a1aff21 — 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-400) exists in github.com/0xJacky/Nginx-UI.
Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI.
Severity: High (CVSS 7.5/10). Risk of unauthorized operations or information disclosure.
Update to 1.9.10-0.20260901043436-8c9b9a1aff21.
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.20260901043436-8c9b9a1aff21ステージング環境で 1.9.10-0.20260901043436-8c9b9a1aff21 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。
-
3Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。