Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
### 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
- Products
- github.com/0xJacky/Nginx-UI
- Affected versions
- Not specified
- Fixed versions
- 1.9.10-0.20260703131214-23d1934099b0
- CVEs
- CVE-2026-84321
- Confirmed fixed CVEs
- Not specified
- Updated in this feed
- 31 Oct 2026, 08:45 UTC · Revision 1
Source evidence
Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
core-osv · Original sourcePublished 15 Oct 2026, 20:14 UTC
### 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
osv:GHSA-wq4w-vwvq-q3x9
github.com/0xJacky/Nginx-UI
Fixed versions: 1.9.10-0.20260703131214-23d1934099b0
Complete source record
{
"id": "fbdaa6558d3e974ccb23ed2ceb69020a4e646c0dbcda61278e45c372e4133049",
"url": "https://osv.dev/vulnerability/GHSA-wq4w-vwvq-q3x9",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable",
"summary": "### 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",
"evidence": "osv:GHSA-wq4w-vwvq-q3x9",
"products": [
{
"name": {
"value": "github.com/0xJacky/Nginx-UI",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.9.10-0.20260703131214-23d1934099b0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "medium",
"structured": {
"id": "GHSA-wq4w-vwvq-q3x9",
"aliases": [
"CVE-2026-84321",
"GHSA-wq4w-vwvq-q3x9",
"GO-2026-6801"
],
"metrics": [
{
"type": "CVSS_V3",
"score": "CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N"
}
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.9.10-0.20260703131214-23d1934099b0"
}
]
}
],
"package": {
"name": "github.com/0xJacky/Nginx-UI",
"purl": "pkg:golang/github.com/0xJacky/Nginx-UI",
"ecosystem": "Go"
},
"database_specific": {
"source": "https://github.com/github/advisory-database/blob/main/advisories/github-reviewed/2026/10/GHSA-wq4w-vwvq-q3x9/GHSA-wq4w-vwvq-q3x9.json"
}
}
],
"modified": "2026-10-19T21:41:20.936879864Z",
"provider": "osv",
"references": [
"https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-wq4w-vwvq-q3x9",
"https://nvd.nist.gov/vuln/detail/CVE-2026-84321",
"https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2",
"https://github.com/0xJacky/nginx-ui",
"https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1"
],
"provider_metadata": {
"cwe_ids": [
"CWE-613"
],
"severity": "MODERATE",
"github_reviewed": true,
"nvd_published_at": "2026-10-12T21:17:22Z",
"github_reviewed_at": "2026-10-15T20:14:01Z"
}
},
"related_cves": [
{
"value": "CVE-2026-84321",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": "/severity/0/score"
},
"source_id": "core-osv",
"document_id": 376801,
"published_at": "2026-10-15T20:14:01+00:00"
}Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable in github.com/0xJacky/Nginx-UI
core-osv · Original sourcePublished 19 Oct 2026, 21:08 UTC
Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable in github.com/0xJacky/Nginx-UI
osv:GO-2026-6801
github.com/0xJacky/Nginx-UI
Fixed versions: 1.9.10-0.20260703131214-23d1934099b0
Complete source record
{
"id": "c4bed279071ceed8cca2393f0ccce55a1a62f8f142f3f0f4fe442a5d0bcc8ac2",
"url": "https://osv.dev/vulnerability/GO-2026-6801",
"method": "structured",
"payload": {
"kind": "advisory",
"title": "Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable in github.com/0xJacky/Nginx-UI",
"summary": "Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable in github.com/0xJacky/Nginx-UI",
"evidence": "osv:GO-2026-6801",
"products": [
{
"name": {
"value": "github.com/0xJacky/Nginx-UI",
"evidence": "/affected/0/package/name"
},
"prerequisites": [],
"fixed_versions": [
{
"value": "1.9.10-0.20260703131214-23d1934099b0",
"evidence": "/affected/0/ranges"
}
],
"affected_versions": []
}
],
"severity": "unknown",
"structured": {
"id": "GO-2026-6801",
"aliases": [
"CVE-2026-84321",
"GHSA-wq4w-vwvq-q3x9",
"GO-2026-6801"
],
"affected": [
{
"ranges": [
{
"type": "SEMVER",
"events": [
{
"introduced": "0"
},
{
"fixed": "1.9.10-0.20260703131214-23d1934099b0"
}
]
}
],
"package": {
"name": "github.com/0xJacky/Nginx-UI",
"purl": "pkg:golang/github.com/0xJacky/Nginx-UI",
"ecosystem": "Go"
},
"database_specific": {
"source": "https://vuln.go.dev/ID/GO-2026-6801.json"
},
"ecosystem_specific": {}
}
],
"modified": "2026-10-19T21:31:53.420955791Z",
"provider": "osv",
"references": [
"https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-wq4w-vwvq-q3x9",
"https://nvd.nist.gov/vuln/detail/CVE-2026-84321",
"https://github.com/0xJacky/nginx-ui/commit/23d1934099b05b2a01589b48129dc3d3159d91c2",
"https://github.com/0xJacky/nginx-ui/releases/tag/v2.4.1"
],
"provider_metadata": {
"url": "https://pkg.go.dev/vuln/GO-2026-6801",
"review_status": "UNREVIEWED"
}
},
"related_cves": [
{
"value": "CVE-2026-84321",
"evidence": "/aliases"
}
],
"security_relevant": true,
"severity_evidence": null
},
"source_id": "core-osv",
"document_id": 376722,
"published_at": "2026-10-19T21:08:35+00:00"
}