Servers and applications
CVE-2026-33031
Disabled users retain full API access through previously issued bearer tokens
- Severity
- High 8.6
- Published
- 18 Apr 2026
- Last changed
- 26 Oct 2026
- Added to UpHeron
- 1 Nov 2026
- Fixed in
- 2.3.3, 2.3.4
- Exploit chance
- 0.3% in the next 30 daysHigher than 20% of CVEs. EPSS by FIRST, 19 Nov 2026
- Attack
- Over the network · Needs a user account · No user action needed
- Attacker can
- Read data · Change data
- CVSS vector
CVSS:4.0/AV:N/AC:L/AT:N/PR:L/UI:N/VC:H/VI:H/VA:N/SC:N/SI:N/SA:N/E:X/CR:X/IR:X/AR:X/MAV:X/MAC:X/MAT:X/MPR:X/MUI:X/MVC:X/MVI:X/MVA:X/MSC:X/MSI:X/MSA:X/S:X/AU:X/R:X/V:X/RE:X/U:X- Also known as
- GHSA-x234-x5vq-cc2v
- Sources
- NVD, Project advisories (GitHub)
Description
A user who was disabled by an administrator can use previously issued API tokens for up to the token lifetime. In practice, disabling a compromised account does not actually terminate that user’s access, so an attacker who already stole a JWT can continue reading and modifying protected resources after the account is marked disabled.
Since tokens can be used to create new accounts, it is possible the disabled user to maintain the privilege.
The application exposes an account-level disable control through the users management API. Login process correctly enforces that control: https://github.com/0xJacky/nginx-ui/blob/6ec542fd97abf2c5950f374f78a32938ad0030e6/internal/user/login.go#L29-L31
However, token-based authentication does not enforce the same check (This code validates token structure and expiry, but returns that user object without checking user.Status.): https://github.com/0xJacky/nginx-ui/blob/6ec542fd97abf2c5950f374f78a32938ad0030e6/internal/user/user.go#L44-L139
Affected software
| Software | Affected versions |
|---|---|
Nginx UIServers and applications · cpe:a:nginxui: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
- NVD https://nvd.nist.gov/vuln/detail/CVE-2026-33031
- CVE.org https://www.cve.org/CVERecord?id=CVE-2026-33031
- GitHub Advisory Database https://github.com/advisories/GHSA-x234-x5vq-cc2v
- github.com https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-x234-x5vq-cc2v