Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable

[ Why it matters ]Priority signals

• Public proof-of-concept exploit exists (CISA SSVC)

[ Description ]Official description

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.

[ Fixes ]Fixes and patches

• github.com/0xJacky/Nginx-UI 1.9.10-0.20260703131214-23d1934099b0Fixed version · GitHub Advisories · go package github.com/0xJacky/Nginx-UI: upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later (affected < 1.9.10-0.20260703131214-23d1934099b0)

[ Packages ]Affected open-source packages

• github.com/0xJacky/Nginx-UI goAffected < 1.9.10-0.20260703131214-23d1934099b0 · fixed in 1.9.10-0.20260703131214-23d1934099b0 · GHSA-wq4w-vwvq-q3x9

[ References ]References

• github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2
• github.com/0xJacky/nginx-ui/releases/tag/v2.4.1
• github.com/0xJacky/nginx-ui/security/advisories/GHSA-wq4w-vwvq-q3x9