How severe is GHSA-x234-x5vq-cc2v?

GHSA-x234-x5vq-cc2v has a CVSS score of 8.1/10, rated HIGH. Immediate patching is strongly recommended.

Which packages are affected by GHSA-x234-x5vq-cc2v?

GHSA-x234-x5vq-cc2v affects the following packages: github.com/0xJacky/Nginx-UI (Go). Ecosystems affected: Go.

How do I fix GHSA-x234-x5vq-cc2v?

Update github.com/0xJacky/Nginx-UI to 1.9.10-0.20260314152518-7b66578adb47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x234-x5vq-cc2v is resolved across your whole dependency graph.

How do I detect GHSA-x234-x5vq-cc2v in my Go dependencies?

Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/0xJacky/Nginx-UI. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.

How do I mitigate GHSA-x234-x5vq-cc2v if there is no patch (or I can't update yet)?

If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.

How does O3 Security protect against GHSA-x234-x5vq-cc2v?

O3 pinpoints whether GHSA-x234-x5vq-cc2v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Is GHSA-x234-x5vq-cc2v actively exploited in the wild?

No public exploit code has been indexed for GHSA-x234-x5vq-cc2v yet. This does not mean the vulnerability cannot be exploited — absence of public exploits does not imply safety. Apply the recommended fix and use O3 Security to monitor your exposure.

When was GHSA-x234-x5vq-cc2v published, and has it been updated?

GHSA-x234-x5vq-cc2v was published on April 21, 2026 and was last updated on June 25, 2026. Advisory data evolves as severity scores, affected ranges, and exploit intelligence are revised — always check the latest version of the advisory before acting.

🐹 Go

GHSA-x234-x5vq-cc2v

HIGHFix: 0xJacky/nginx-ui@7b66578

GHSA-x234-x5vq-cc2v is a high-severity (CVSS 8.1) vulnerability in github.com/0xJacky/Nginx-UI. O3 Security confirms whether GHSA-x234-x5vq-cc2v is actually reachable in your code before you act, and blocks exploitation at runtime until you patch.

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

Also known asCVE-2026-33031GO-2026-5733

Published

Apr 21, 2026

Updated

Jun 25, 2026

Affected

1 pkg

Patched

1 / 1

Exploits

None indexed

Real-World Exposure

1 pkg affected

🐹github.com/0xJacky/Nginx-UI

Real-time download stats are indexed for npm and PyPI packages. This vulnerability affects Go packages — download data is not available via public APIs for these ecosystems.

Description

Summary

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.

Details

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

There’s also no token revocation feature, unlike when a password is changed: https://github.com/0xJacky/nginx-ui/blob/6ec542fd97abf2c5950f374f78a32938ad0030e6/api/user/user.go#L38-L51

As a result, a disabled user can continue to have full API access. In particular, since that includes account creation, they can create a new account and keep operating even after the JWT expires.

PoC

The issue was validated with version 2.3.3 using the uozi/nginx-ui:sha-c92ec0a docker image.

View the PoC video:

https://github.com/user-attachments/assets/7a5175cb-2f79-4c1b-adad-e7d0bf2ea2bd

Impact

Administrators who rely on "disable user" as an authentication or authorization control can be bypassed.

The disabled user can keep reading sensitive configuration and executing authenticated state-changing actions allowed to that account.

Affected Packages

1 total 1 fixed

Ecosystem	Package	Vulnerable range	Fix
🐹Go	`github.com/0xJacky/Nginx-UI`	all versions	1.9.10-0.20260314152518-7b66578adb47

Detection & mitigation playbook

Open-source dependency

Detect
Scan your dependency tree (package-lock.json, pnpm-lock.yaml, requirements.txt, go.sum, etc.) for github.com/0xJacky/Nginx-UI. O3's reachability analysis confirms whether the vulnerable code path is actually invoked in your application, so you act on real exposure instead of every transitive match.
Fix
Update github.com/0xJacky/Nginx-UI to 1.9.10-0.20260314152518-7b66578adb47 or later, then make sure no transitive (indirect) dependency still pins the vulnerable range — O3 confirms GHSA-x234-x5vq-cc2v is resolved across your whole dependency graph.
Workarounds
If you can't upgrade right away: gate or disable the affected feature, validate untrusted input at the boundary, and avoid passing attacker-controlled data into the vulnerable path. O3's runtime protection blocks exploitation in production as an interim safeguard until the upgrade lands.
How O3 protects you
O3 pinpoints whether GHSA-x234-x5vq-cc2v is reachable in your code and exactly where to fix it, then blocks exploitation in production at runtime until the patched version is deployed.

Tailored to GHSA-x234-x5vq-cc2v. Runtime protection reduces exposure until a permanent patch is applied and verified — it complements patching, it doesn't replace it.

Frequently Asked Questions

### Summary 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. ### Details The application exposes an account-level disable control through the users management API. Login process correctly enforces tha

O3 Security · Impact-Aware SCA

Is GHSA-x234-x5vq-cc2v in your dependencies?

O3 detects GHSA-x234-x5vq-cc2v across Go dependencies and uses function-level reachability to confirm whether the vulnerable code path is actually reachable — not just present. No false positives.

Scan my dependencies How O3 SCA works