Sign in Sign up
JA · EN · FR
SecPulse
Categories
CVE-2026-84320 medium CVSS 6.3

Path Traversal in github.com/0xJacky/Nginx-UI (CVE-2026-84320)

Summary

Path traversal in github.com/0xJacky/Nginx-UI (CVE-2026-84320). Risk of unauthorized operations or information disclosure. Exploitable via backup_path. Mitigation: upgrade to 1.9.10-0.20260715121709-f92218e01054 or later.

Original description

The description as published by the source.

Summary

Nginx UI validates backup_path and storage_path against the administrator-defined backup.GrantedAccessPath boundary, but the final auto-backup output filename is built from the user-controlled auto-backup name without stripping path separators or .. components.

An authenticated user who can create or modify an auto-backup task can set a name such as task/../../../escaped. The configured storage_path still passes validation because it is inside GrantedAccessPath, but the generated backup path escapes that storage directory when filepath.Join(storage_path, filename) resolves the embedded traversal sequence.

This bypasses the documented backup path boundary and allows backup archives, and for encrypted configuration backups the adjacent .key file, to be written outside the intended storage directory with the Nginx UI process privileges.

Affected Versions

  • Current dev branch commit checked: 4948fba8744e82c3d7003f68ee164e9f49421066
  • Latest release checked: v2.3.10, published 2026-04-28
  • The vulnerable filename construction is present in both current dev and v2.3.10.

Security Boundary

The project documentation describes backup.GrantedAccessPath as the critical security boundary for backup operations. It says the setting:

  • restricts backup operations to explicitly authorized directories,
  • prevents unauthorized access to sensitive system directories,
  • enforces administrator-defined boundaries,
  • normalizes paths to preven…

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-84320 has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like backup_path over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: 6.3/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260715121709-f92218e01054 or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-84320" on the vendor's site.

CVE-2026-84320 (github.com/0xJacky/Nginx-UI) — CWE-22 / CVSS v3 6.3
Attack vector: remote (network-reachable) / no user interaction
Attack surface: backup_path / storage_path / backup.GrantedAccessPath / name
Patched: 1.9.10-0.20260715121709-f92218e01054 — 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

Path traversal (CWE-22) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via backup_path.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: backup_path / storage_path / backup.GrantedAccessPath / name.

🔥 Severity

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

🔧 How to fix

Update to 1.9.10-0.20260715121709-f92218e01054.

🛡️ 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.20260715121709-f92218e01054

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

  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.20260715121709-f92218e01054"}]}]

References

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