Advisory record · GHSA-wq4w-vwvq-q3x9

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

CVSS 5.4 MediumEPSS 0.0021 · 11th percentile

Published by the GitHub Advisory Database at 15 Oct 2026, 20:14 UTC. agentprime has not analysed this yet, so whether it affects any app is not known.

PackageEcosystemAffectedFixed in
github.com/0xJacky/Nginx-UIGo<1.9.10-0.20260703131214-23d1934099b01.9.10-0.20260703131214-23d1934099b0
Identifiers
GHSA-wq4w-vwvq-q3x9 · CVE-2026-84321 · GO-2026-6801
Weakness (CWE)
CWE-613
Published
15 Oct 2026
Updated
19 Oct 2026

Machine-written summary

Summary written by Claude Haiku from the source advisory. Not reviewed by a person.

Nginx UI (github.com/0xJacky/Nginx-UI) versions before 1.9.10-0.20260703131214-23d1934099b0 are affected. When an administrator disables an account and revokes its tokens, standalone short tokens can remain in cache, so if the account is re-enabled before the cache entry expires, a previously revoked short token authenticates again. The source describes this as a local test rather than a broader assessment, and the attacker's required access is not stated in detail beyond holding a stolen short token. Upgrade to 1.9.10-0.20260703131214-23d1934099b0 or later.

Written 1 Nov 2026.

Not analysed yet

We haven’t published our analysis of this Advisory yet. Once a person has reviewed it, this page will say what’s vulnerable, what has to be true for your app to be affected, and how to check.

Severity and exploitation

ScoreRatingCVSSVectorSource
5.4 Medium 3.1 CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:N CNA (GitHub_M)
  • CISA KEV Not listed.
  • EPSS 0.0021, the 11th percentile, on 7 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

Timeline

  1. 31 Oct 2026, 14:11 UTC First seen by agentprime
  2. 31 Oct 2026, 14:11 UTC Confirmed by OSV

Sources

Facts on this page come from the GitHub Advisory Database (CC-BY 4.0), OSV and the other sources listed, as published. We don’t reproduce full advisory descriptions, which can contain exploit code.