Servers and applications
CVE-2026-84321
Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
- Severity
- Medium 5.4
- Published
- 17 Jul 2026
- Last changed
- 13 Oct 2026
- Added to UpHeron
- 3 Nov 2026
- Fixed in
- 2.4.1
- Exploit chance
- 0.2% in the next 30 daysHigher than 11% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read some data · Change some data
- CVSS vector
CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N- Also known as
- GHSA-wq4w-vwvq-q3x9
- Sources
- CVE Program, Project advisories (GitHub)
Description
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.
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
- internal/user/user.go
- internal/user/user.go
- api/user/short_token.go
- internal/middleware/middleware.go
Affected software
| Software | Affected versions |
|---|---|
Nginx UIServers and applications · cna:0xjacky|nginx-ui |
|
Nginx UIServers and applications · github:0xjacky/nginx-ui |
|
About Nginx UI
Yet another WebUI for Nginx
- Docker Hub pulls
- 1,512,532Docker Hub, 15 Nov 2026
- GitHub stars
- 11,783GitHub, 15 Nov 2026
- Forks
- 921GitHub, 15 Nov 2026
- Latest release
- v3.0.3GitHub, 15 Nov 2026
- Released
- 12 Nov 2026GitHub
- License
- AGPL-3.0GitHub
- First published on GitHub
- 19 Feb 2021GitHub
Source code Website Docker image
Vulnerabilities in Nginx UI
- In our list
- 75
- Published in the last 12 months
- 67
- Critical, last 12 months
- 11
- High, last 12 months
- 34
- Known exploited
- 0
- GHSA-57f3-39rr-2mwmNginx-UI certificate path validators read arbitrary absolute paths, enabling a file existence oracle and process-crash DoSLow 3.8 20 Nov 2026
- GHSA-c2cq-7453-7xpjRead-only service tokens still receive stored secrets (incomplete fix of GHSA-pw4f-pq6v-x57r)Medium 6.5 20 Nov 2026
- GHSA-xwxf-xc5j-p7hxDirective denylist bypass via mid-token '#' tokenizer differential (incomplete fix of GHSA-cf23-7qxj-xmhr)High 7.2 20 Nov 2026
- GHSA-2rjr-44wx-8qpgJwtSecret Overwrite via Settings API Causes Session Invalidation and MonopolyLow 3.8 12 Nov 2026
- GHSA-p355-qjwh-8hgmOpenAI API Key Exfiltration via Unprotected BaseUrl Setting ChangeLow 2.7 12 Nov 2026
- GHSA-hf3h-p3fr-3f2rFull backup exports expose reusable interactive login sessions to management credentialsMedium 6.6 12 Nov 2026
References
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-84321
- GitHub Advisory Database https://github.com/advisories/GHSA-wq4w-vwvq-q3x9
- github.com https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-wq4w-vwvq-q3x9