Categories
CVE-2026-84321 medium CVSS 5.4

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

Summary

Vulnerability in github.com/0xJacky/Nginx-UI (CVE-2026-84321). Risk of unauthorized operations or information disclosure. Exploitable via AuthToken. Mitigation: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.

Original description

The description as published by the source.

Summary

Standalone short tokens issued for WebSocket and explicit-token authentication can survive administrative revocation in cache. If the same account is later re-enabled before the cache entry expires, the deleted short token becomes valid again.

Details

GenerateShortToken() creates an AuthToken row that contains only ShortToken and no long Token. DeleteUserTokens() removes database rows, but when clearing caches it only invalidates entries where authToken.Token != "". This leaves standalone short-token cache entries behind. GetTokenUserByShortToken() checks that cache first and then loads the user by ID, so the stale short token becomes usable again if the account status is restored to true.

Relevant code paths:

PoC

This was verfied locally in an isolated environment with a temporary package-level harness that exercised the real token issuance, revocation, cache, and re-authentication paths.

What the executed test did:

  1. Created an enabled user in a temporary SQLite database.
  2. Ca…

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

CVE-2026-84321 (github.com/0xJacky/Nginx-UI) — CWE-613 / CVSS v3 5.4
Attack vector: remote (network-reachable) / no user interaction
Attack surface: AuthToken / ShortToken / Token / true
Patched: 1.9.10-0.20260703131214-23d1934099b0 — 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-613) exists in github.com/0xJacky/Nginx-UI. Attackers reach the vulnerable code path via AuthToken.

📍 Affected scope

Check the vendor advisory for the affected versions of github.com/0xJacky/Nginx-UI. Attack surface: AuthToken / ShortToken / Token / true.

🔥 Severity

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

🔧 How to fix

Update to 1.9.10-0.20260703131214-23d1934099b0.

🛡️ 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.20260703131214-23d1934099b0

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

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

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

Affected packages

go github.com/0xJacky/Nginx-UI
[{"type":"SEMVER","events":[{"introduced":"0"},{"fixed":"1.9.10-0.20260703131214-23d1934099b0"}]}]

References

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