← Back
CVE-2026-33026
Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-33026)
Summary
vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-33026). Risk of unauthorized operations or information disclosure. Exploitable via ``hash_info.txt``. Mitigation: upgrade to `1.9.10-0.20260315015203-f61bcec547c0` or later.
AI summary snake-internal / snake-material-v2
A vulnerability tracked as **CVE-2026-33026** has been found in github.com/0xJacky/Nginx-UI.
Attackers can target a specific entry point like ``hash_info.txt`` over the network to misuse the product.
Risk of unauthorized operations or information disclosure. CVSS score: ?/10.
What to do: upgrade github.com/0xJacky/Nginx-UI to **1.9.10-0.20260315015203-f61bcec547c0** or later.
If unsure, ask your IT team or search "github.com/0xJacky/Nginx-UI CVE-2026-33026" on the vendor's site.
CVE-2026-33026 (github.com/0xJacky/Nginx-UI) — CWE-312 /
Attack surface: `hash_info.txt` / `nginx.zip` / `backup_crypto.go` / `backup.go`
Patched: `1.9.10-0.20260315015203-f61bcec547c0` — 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-312) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via ``hash_info.txt`` without authentication.
📍 Affected scope
github.com/0xJacky/Nginx-UI — . Attack surface: `hash_info.txt` / `nginx.zip` / `backup_crypto.go` / `backup.go`.
🔥 Severity
Severity: ?. Risk of unauthorized operations or information disclosure
🔧 How to fix
Update to **1.9.10-0.20260315015203-f61bcec547c0**.
🛡️ 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.20260315015203-f61bcec547c0ステージング環境で 1.9.10-0.20260315015203-f61bcec547c0 に上げて回帰テスト → 本番反映。回帰テストはアプリの主要ハッピーパスと、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.20260315015203-f61bcec547c0"}]}]
References
- advisory https://github.com/advisories/GHSA-g9w5-qffc-6762
- advisory https://nvd.nist.gov/vuln/detail/CVE-2026-33026
- package https://github.com/0xJacky/nginx-ui
- web https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-fhh2-gg7w-gwpq
- web https://github.com/0xJacky/nginx-ui/releases/tag/v2.3.4
- web https://github.com/0xJacky/nginx-ui/commit/f61bcec547c0f305e35348d6440ef156c1d5c3cb
- web https://pkg.go.dev/vuln/GO-2026-4903
- web https://github.com/advisories/GHSA-fhh2-gg7w-gwpq