CVE-2026-84321: Nginx UI Standalone Short Tokens Survive Administrative Vulnerability

MODERATE
Advisory Identifier: GHSA-wq4w-vwvq-q3x9
CVSS 5.4
CWE-613
Published
Advisory Summary

CVE-2026-84321 is a MODERATE (CVSS 5.4) standalone short tokens survive administrative vulnerability (CWE-613: Insufficient Session Expiration) affecting Nginx UI libraries in the Go ecosystem. The issue involves standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable. Remediation is available by upgrading affected packages to version 1.9.10-0.20260703131214-23d1934099b0.

CVE-2026-84321 at a Glance

CVE Identifier CVE-2026-84321
GHSA Identifier GHSA-wq4w-vwvq-q3x9
Severity MODERATE
CVSS v3.1 Base Score 5.4
CWE Classification CWE-613: Insufficient Session Expiration
Affected Product Nginx UI
Package Ecosystem Go
Published Date
Last Updated

Security Impact

CVSS: 5.4

The security impact metrics below are parsed directly from the CVSS v3.1 vector string (CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N).

Attack Vector Network (AV:N)
Attack Complexity Low (AC:L)
Privileges Required Low (PR:L)
User Interaction None (UI:N)
Scope Unchanged (S:U)
Confidentiality Low (C:L)
Integrity Low (I:L)
Availability None (A:N)

How to Fix CVE-2026-84321

To remediate this vulnerability, upgrade all affected Nginx UI dependencies to a patched release. Both direct and transitive dependencies should be checked, as frameworks or security libraries may pull in vulnerable versions transitively.

github.com/0xJacky/Nginx-UI fixed: 1.9.10-0.20260703131214-23d1934099b0
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260703131214-23d1934099b0
Verify Direct and Transitive Dependencies

Run the following command in your project directory to verify that all resolved dependencies use the patched release:

inspect dependencies for github.com/0xJacky/Nginx-UI

How to Check if You Are Affected

To determine whether your application is affected by CVE-2026-84321, inspect your project dependencies for Nginx UI:

inspect dependencies for github.com/0xJacky/Nginx-UI

Analyze the terminal output to locate any version of Nginx UI in your dependency tree. If any resolved version matches the vulnerable ranges listed in the table below (for example, versions earlier than 1.9.10-0.20260703131214-23d1934099b0), your application is affected.

Note: Verify declared build manifests and deployed runtime container environments.

Technical Details

Vulnerability Mechanism & Technical Analysis

This vulnerability is classified under CWE-613: Insufficient Session Expiration, where according to wasc, "insufficient session expiration is when a web site permits an attacker to reuse old session credentials or session ids for authorization.". In Nginx UI, software state validation or input boundaries are circumvented during processing. Review the official source advisory statement below for specific affected components, classes, and reproduction details.

Source Advisory Statement

### 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: - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:43) - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:118) - [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:204) - [api/user/short_token.go](/home/kali/Desktop/bounty/nginx-ui/api/user/short_token.go:13) - [internal/middleware/middleware.go](/home/kali/Desktop/bounty/nginx-ui/internal/middleware/middleware.go:82) ### 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. Called the real `GenerateShortToken(user.ID)` function to issue a standalone short token. 3. Verified that the token authenticated successfully and was present in the short-token cache. 4. Disabled the user and called the real `DeleteUserTokens(user.ID)` function. 5. Verified that the database token rows were removed. 6. Verified that the short-token cache entry still existed after `DeleteUserTokens`. 7. Re-enabled the same user. 8. Reused the previously deleted short token via the real `GetTokenUserByShortToken()` path and observed successful authentication. Observed result from the actual local verification: - The database token rows were removed during revocation. - The short-token cache entry remained present. - Re-enabling the user restored successful authentication through the stale short token. ### Impact Any deployment using standalone short tokens is affected. If a short token is stolen, administrative disable/delete-token handling may not fully revoke it. Re-enabling the account within the cache lifetime restores access for the stale token to any HTTP or WebSocket routes that accept short-token authentication.

CVE-2026-84321 Affected Nginx UI Versions

1 component(s)
Fixed Versions:
1.9.10-0.20260703131214-23d1934099b0
Product / Package Ecosystem Affected Versions Fixed Version
github.com/0xJacky/Nginx-UI
Go
< 1.9.10-0.20260703131214-23d1934099b0
1.9.10-0.20260703131214-23d1934099b0

References

Frequently Asked Questions

What is CVE-2026-84321?
CVE-2026-84321 is a security vulnerability in Nginx UI involving Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable under CWE-613: Insufficient Session Expiration.
Which Nginx UI versions are affected?
Affected versions include releases prior to 1.9.10-0.20260703131214-23d1934099b0 across affected packages: github.com/0xJacky/Nginx-UI.
What version fixes CVE-2026-84321?
Upgrading to 1.9.10-0.20260703131214-23d1934099b0 (or the latest patched release for your respective branch) resolves the vulnerability.
Is github.com/0xJacky/Nginx-UI affected?
Yes, github.com/0xJacky/Nginx-UI is affected in releases prior to 1.9.10-0.20260703131214-23d1934099b0. Upgrade your dependency to 1.9.10-0.20260703131214-23d1934099b0 or later.
What is the CVSS score of CVE-2026-84321?
CVE-2026-84321 has a CVSS v3.1 base score of 5.4 (MODERATE) with vector string CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N.
What CWE is associated with CVE-2026-84321?
CVE-2026-84321 is classified under CWE-613: Insufficient Session Expiration (According to WASC, "Insufficient Session Expiration is when a web site permits an attacker to reuse old session credentials or session IDs for authorization.").
How can I check Go dependencies for CVE-2026-84321?
Run the dependency tree command: 'inspect dependencies for github.com/0xJacky/Nginx-UI'. This command lists direct and transitive dependencies in your build configuration so you can verify if a vulnerable version is resolved.
Machine-readable OSV JSON OSV v1.5 Schema
Normalized schema output
{
  "schema_version" : "1.4.0",
  "id" : "GHSA-wq4w-vwvq-q3x9",
  "modified" : "2026-10-15T20:14:01Z",
  "published" : "2026-10-15T20:14:01Z",
  "aliases" : [ "CVE-2026-84321" ],
  "summary" : "Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable",
  "details" : "### Summary\nStandalone 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.\n\n### Details\n`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`.\n\nRelevant code paths:\n- [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:43)\n- [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:118)\n- [internal/user/user.go](/home/kali/Desktop/bounty/nginx-ui/internal/user/user.go:204)\n- [api/user/short_token.go](/home/kali/Desktop/bounty/nginx-ui/api/user/short_token.go:13)\n- [internal/middleware/middleware.go](/home/kali/Desktop/bounty/nginx-ui/internal/middleware/middleware.go:82)\n\n### PoC\nThis 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.\n\nWhat the executed test did:\n1. Created an enabled user in a temporary SQLite database.\n2. Called the real `GenerateShortToken(user.ID)` function to issue a standalone short token.\n3. Verified that the token authenticated successfully and was present in the short-token cache.\n4. Disabled the user and called the real `DeleteUserTokens(user.ID)` function.\n5. Verified that the database token rows were removed.\n6. Verified that the short-token cache entry still existed after `DeleteUserTokens`.\n7. Re-enabled the same user.\n8. Reused the previously deleted short token via the real `GetTokenUserByShortToken()` path and observed successful authentication.\n\nObserved result from the actual local verification:\n- The database token rows were removed during revocation.\n- The short-token cache entry remained present.\n- Re-enabling the user restored successful authentication through the stale short token.\n\n### Impact\nAny deployment using standalone short tokens is affected. If a short token is stolen, administrative disable/delete-token handling may not fully revoke it. Re-enabling the account within the cache lifetime restores access for the stale token to any HTTP or WebSocket routes that accept short-token authentication.",
  "severity" : [ {
    "type" : "CVSS_V3",
    "score" : "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
  } ],
  "affected" : [ {
    "package" : {
      "ecosystem" : "Go",
      "name" : "github.com/0xJacky/Nginx-UI"
    },
    "ranges" : [ {
      "type" : "ECOSYSTEM",
      "events" : [ {
        "introduced" : "0"
      }, {
        "fixed" : "1.9.10-0.20260703131214-23d1934099b0"
      } ]
    } ]
  } ],
  "references" : [ {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-wq4w-vwvq-q3x9"
  }, {
    "type" : "ADVISORY",
    "url" : "https://nvd.nist.gov/vuln/detail/CVE-2026-84321"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2"
  }, {
    "type" : "PACKAGE",
    "url" : "https://github.com/0xJacky/nginx-ui"
  }, {
    "type" : "WEB",
    "url" : "https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1"
  } ],
  "database_specific" : {
    "cwe_ids" : [ "CWE-613" ],
    "severity" : "MODERATE",
    "github_reviewed" : true,
    "github_reviewed_at" : "2026-10-15T20:14:01Z",
    "nvd_published_at" : "2026-10-12T21:17:22Z"
  }
}