← Back
CVE-2026-33031
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-33031)
Summary
vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-33031). Confidential information can be exposed externally. Exploitable via ``user.Status``. Mitigation: upgrade to `1.9.10-0.20260314152518-7b66578adb47` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33031** has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like ``user.Status`` over the network to misuse the product.
Confidential information can be exposed externally. CVSS score: ?/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to **1.9.10-0.20260314152518-7b66578adb47** or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-33031" on the vendor's site.
CVE-2026-33031 (github.com/0xJacky/Nginx-UI) — CWE-284 /
Attack vector: remote (network-reachable) / no user interaction
Attack surface: `user.Status`
Patched: `1.9.10-0.20260314152518-7b66578adb47` — 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-284) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via ``user.Status`` without authentication.
📍 Affected scope
github.com/0xJacky/Nginx-UI — . Attack surface: `user.Status`.
🔥 Severity
Severity: ?. Confidential information can be exposed externally
🔧 How to fix
Update to **1.9.10-0.20260314152518-7b66578adb47**.
🛡️ 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 (7 steps)
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 し、稼働しているサービス・バージョンを把握する。
-
6Apply patch patch
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260314152518-7b66578adb47ステージング環境で 1.9.10-0.20260314152518-7b66578adb47 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、Step 3 で見つけた異常検知の続報チェックを含めること。
-
7Post-deployment verification verify
Confirm patched version is live in productionパッチ適用後、ステージングで PoC または同等の悪用パターンを再現して脆弱性が閉じたことを確認。本番では Step 3 と同じログクエリでアラート再発が無いか継続監視。
Affected packages
Go
github.com/0xJacky/Nginx-UI
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.9.10-0.20260314152518-7b66578adb47"}]}]
References
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33031
- package https://github.com/0xJacky/nginx-ui
- web https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-x234-x5vq-cc2v
- web https://github.com/0xJacky/nginx-ui/commit/7b66578adb47bbec839b621a4666495249379174
- web https://github.com/0xJacky/nginx-ui/releases/tag/v2.3.4