Categories
CVE-2026-107804 medium CVSS 5.3

Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-107804)

Summary

Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-107804). Risk of unauthorized operations or information disclosure. Mitigation: upgrade to 1.9.10-0.20260904075558-e30e331303fc or later.

Original description

The description as published by the source.

Summary

In Nginx UI versions 2.2.0 through 2.5.x, the official bundled reverse-proxy topology did not preserve the external client identity used by Gin. The backend treated the local proxy peer as the client because no trusted proxy was configured, while the proxy supplied the actual address in forwarding headers.

Impact

This has two distinct effects in bundled-proxy deployments:

  • IP allowlist enforcement: management API requests forwarded by the bundled proxy were identified as loopback and could pass the loopback exception even when the external source was not in the configured allowlist. Protected management operations still required valid credentials; this did not grant unauthenticated administrator access.
  • Login availability: failed login attempts from different external sources were attributed to one loopback address. An unauthenticated attacker could therefore trigger the shared temporary login-ban threshold and deny password or OTP login to other users behind the proxy until the ban expired. Existing authenticated sessions were not invalidated.

Remediation

Upgrade to Nginx UI 2.6.0 or later. The fix explicitly trusts only the intended bundled proxy, validates configured trusted proxies, uses the resolved client address consistently, and fails closed when an IP allowlist is enabled but the client address is invalid.

Fix commit: https://github.com/0xJacky/nginx-ui/commit/e30e331303fc21cf077a2bea724bd79e66892eaf

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-107804 has been found in github.com/0xJacky/Nginx-UI.
Risk of unauthorized operations or information disclosure. CVSS score: 5.3/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260904075558-e30e331303fc or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-107804" on the vendor's site.

CVE-2026-107804 (github.com/0xJacky/Nginx-UI) — CWE-346 / CVSS v3 5.3
Attack vector: remote (network-reachable) / unauthenticated / no user interaction
Patched: 1.9.10-0.20260904075558-e30e331303fc — 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.

❓ What is the problem

A vulnerability (CWE-346) exists in github.com/0xJacky/Nginx-UI.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI.

🔥 Severity

Severity: Medium (CVSS 5.3/10). Risk of unauthorized operations or information disclosure.

🔧 How to fix

Update to 1.9.10-0.20260904075558-e30e331303fc.

🛡️ Workaround

Until the patch is applied: disable the affected feature, apply WAF rules, or restrict access via network ACLs.

🔍 Detection

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

  1. 1
    Identify 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 し、稼働しているサービス・バージョンを把握する。

  2. 2
    Apply patch patch
    Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260904075558-e30e331303fc

    ステージング環境で 1.9.10-0.20260904075558-e30e331303fc に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスを含めること。

  3. 3
    Post-deployment verification verify
    Confirm patched version is live in production

    パッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番ではアクセスログ・WAF でアラート再発が無いか継続監視。

Affected packages

go github.com/0xJacky/Nginx-UI
[{"type":"ECOSYSTEM","events":[{"introduced":"0"},{"fixed":"1.9.10-0.20260904075558-e30e331303fc"}]}]

References

We use cookies for analytics and ad measurement. This setting applies to all Game co., Ltd. sites. Details