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

Exploitation

No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.

CVSS

5.4 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N

EPSS

• CVE-2026-84321: 0.21% estimated exploitation activity in the next 30 days; percentile 11.21 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.

As published by the source; long descriptions are shortened.

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 - internal/user/user.go - internal/user/user.go - api/user/shorttoken.go - internal/middleware/middleware.go PoC This was verfied locally in an isolated environment with a temporary package-level harness that exercised the real token issuance,…

Published by the source

15 Oct 2026, 20:14 UTC

Last modified by the source

19 Oct 2026, 21:31 UTC

Source last checked

26 Oct 2026, 15:32 UTC

1. Revision 3 · amended · 26 Oct 2026

   Amended from ghsa record GHSA-wq4w-vwvq-q3x9

2. Revision 2 · amended · 24 Oct 2026

   Amended from osv record GO-2026-6801

3. Revision 1 · created · 24 Oct 2026

   Published from osv record GHSA-wq4w-vwvq-q3x9

Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.

# Patch Next advisory brief: CVE-2026-84321

Advisory: Nginx UI: Standalone short tokens survive administrative revocation in cache and authenticate again after account re-enable
IDs: CVE-2026-84321, GHSA-wq4w-vwvq-q3x9
Record: https://patchnext.com/advisories/cve-2026-84321 (revision 3, source checked 26 Oct 2026, 15:32 UTC)
Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected.
Severity: Medium (CVSS 5.4)
Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV.
Vendor response: Vendor fix available; fixed versions by package: github.com/0xJacky/Nginx-UI 1.9.10-0.20260703131214-23d1934099b0. A vendor fix does not mean a deployment is fixed.

## Affected components
- Go github.com/0xJacky/Nginx-UI: affected < 1.9.10-0.20260703131214-23d1934099b0; fixed in 1.9.10-0.20260703131214-23d1934099b0

## Suggested inspection (read-only)
- Go github.com/0xJacky/Nginx-UI: check the installed version with your package manager.

## Supported action
Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version.

## Required regression checks
- Run the test suite and a production build.
- Exercise the features that depend on github.com/0xJacky/Nginx-UI.
- Repeat the inspection and confirm that only fixed versions remain installed.

## Rollback considerations
- Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward.

## Unresolved questions
- Which deployments run an affected version?
- Exploitation status can change. Check again before lowering the priority.
- Mark the work resolved only after the fixed version is verified in production.

## Sources
- Verified: https://osv.dev/vulnerability/GO-2026-6801 (OSV record GO-2026-6801 lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260703131214-23d1934099b0 (fixed))
- Verified: https://osv.dev/vulnerability/GHSA-wq4w-vwvq-q3x9 (OSV record GHSA-wq4w-vwvq-q3x9 lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260703131214-23d1934099b0 (fixed))
- Verified: https://github.com/advisories/GHSA-wq4w-vwvq-q3x9 (GitHub-reviewed advisory GHSA-wq4w-vwvq-q3x9 lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260703131214-23d1934099b0)

Commands are suggestions: review each one before running it.