CVE-2026-84321 — Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, GenerateShortToken creates standalone short-token records without a long Token value, but DeleteUserTo…
Published: 2026-10-12 · CVSS: 5.4 · CVSS 3.1
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.1, GenerateShortToken creates standalone short-token records without a long Token value, but DeleteUserTokens invalidates cached entries only when the long Token field is nonempty. A revoked short token can therefore remain in the short_token cache and authenticate again if the associated account is re-enabled before the cache entry expires because GetTokenUserByShortToken reads the surviving entry, restoring access to HTTP or WebSocket routes that accept short-token authentication. This issue is fixed in version 2.4.1.
Source: CVE Program · Revision 8b16575c39f1e1810c5e863010da073d2d3285e7