# Nginx-UI: Disabled users retain full API access through previously issued bearer tokens

Advisory record · `GHSA-x234-x5vq-cc2v`

- **Identifiers:** `GHSA-x234-x5vq-cc2v` · `CVE-2026-33031` · `GO-2026-5733`
- **State:** Confirmed
- **Severity:** CVSS 8.6 High
- **Critical:** No
- **Weakness (CWE):** [CWE-284](https://cwe.mitre.org/data/definitions/284.html) · [CWE-863](https://cwe.mitre.org/data/definitions/863.html)
- **Tags:** [Broken access control](https://agentprime.io/advisories/tag/access-control.md)
- **Published:** 21 Apr 2026
- **Updated:** 25 Jun 2026
- **Reviewed by a person:** No

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

## Affected packages

- `github.com/0xJacky/Nginx-UI` (Go): affected `<1.9.10-0.20260314152518-7b66578adb47`; fixed in `1.9.10-0.20260314152518-7b66578adb47`

## Machine-written summary

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

> Nginx-UI (Go module github.com/0xJacky/Nginx-UI) versions before 1.9.10-0.20260314152518-7b66578adb47 are affected. Token-based authentication does not check whether a user has been disabled, so a user disabled by an administrator can keep using previously issued API tokens until they expire and can still read and change protected resources, including creating new accounts. Upgrade to 1.9.10-0.20260314152518-7b66578adb47 or later. No workaround is given in the source.

Written 6 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

- 8.6 High, CVSS 4.0: `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`, from CNA (GitHub_M)

- **CISA KEV:** Not listed.
- **EPSS:** 0.0028, the 20th percentile, on 18 Nov 2026: FIRST’s estimate of the chance of exploitation in the next 30 days.

## Timeline

- 31 Oct 2026, 15:06 UTC: First seen by agentprime
- 31 Oct 2026, 15:06 UTC: [Confirmed by OSV](https://osv.dev/vulnerability/GHSA-x234-x5vq-cc2v)

## Sources

- [GitHub Advisory Database: GHSA-x234-x5vq-cc2v](https://github.com/advisories/GHSA-x234-x5vq-cc2v)
- [OSV: GHSA-x234-x5vq-cc2v](https://osv.dev/vulnerability/GHSA-x234-x5vq-cc2v)
- <https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-x234-x5vq-cc2v>
- <https://nvd.nist.gov/vuln/detail/CVE-2026-33031>
- <https://github.com/0xJacky/nginx-ui/commit/7b66578adb47bbec839b621a4666495249379174>
- <https://github.com/0xJacky/nginx-ui>
- <https://github.com/0xJacky/nginx-ui/releases/tag/v2.3.4>

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.

## Check whether this affects you

A Match means an installed version is in the affected range above. Most don’t affect the app; agentprime hasn’t analysed this one yet.

- With the agentprime MCP server (<https://api.agentprime.io/mcp>), ask your agent to check the project: `check_lockfile` sends a lockfile, `check_packages` a list of installed packages, and both return the Matches and the upgrades that clear them. `get_advisory` returns this record. Setup: <https://agentprime.io/mcp.md>
- In a browser: <https://agentprime.io/check/> reads your lockfile in the browser, never uploading it.
- Whether it touches your code, with file and line: the Claude Code plugin, <https://agentprime.io/plugin.md>
- As JSON: <https://api.agentprime.io/v1/advisories/GHSA-x234-x5vq-cc2v>, or `POST https://api.agentprime.io/v1/match` with your packages (<https://agentprime.io/api.md>)

---

The web page: <https://agentprime.io/advisories/GHSA-x234-x5vq-cc2v/>. Everything for agents: <https://agentprime.io/llms.txt>.
