Is CVE-2026-33031 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-33031 being exploited in the wild.

How severe is CVE-2026-33031?

High severity, with a CVSS score of 8.1, published 20 April 2026.

Which products and versions are affected?

github.com/0xJacky/Nginx-UI (Go) < 1.9.10-0.20260314152518-7b66578adb47, SEMVER:introduced=0,fixed=1.9.10-0.20260314152518-7b66578adb47.

Is there a fix for CVE-2026-33031?

Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260314152518-7b66578adb47 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Am I affected by CVE-2026-33031?

Check whether you run github.com/0xJacky/Nginx-UI (Go) or Nginxui Nginx Ui at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

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

Q: Is there a fix for CVE-2026-33031?

Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260314152518-7b66578adb47 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: Am I affected by CVE-2026-33031?

Check whether you run github.com/0xJacky/Nginx-UI (Go) or Nginxui Nginx Ui at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-33031 · Severity: high · CVSS 8.1 · Published 2026-04-20

Nginx UI is a web user interface for the Nginx web server. Prior to version 2.3.4, 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. Version 2.3.4 patches the issue.

Technologies: github.com/0xJacky/Nginx-UI (Go), Nginxui Nginx Ui. Vendors: Go, Nginxui.

Quick answers

Is CVE-2026-33031 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-33031 being exploited in the wild.
How severe is CVE-2026-33031?: High severity, with a CVSS score of 8.1, published 20 April 2026.
Which products and versions are affected?: github.com/0xJacky/Nginx-UI (Go) < 1.9.10-0.20260314152518-7b66578adb47, SEMVER:introduced=0,fixed=1.9.10-0.20260314152518-7b66578adb47.
Is there a fix for CVE-2026-33031?: Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260314152518-7b66578adb47 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
Am I affected by CVE-2026-33031?: Check whether you run github.com/0xJacky/Nginx-UI (Go) or Nginxui Nginx Ui at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260314152518-7b66578adb47 or later
```
go get github.com/0xJacky/Nginx-UI@v1.9.10-0.20260314152518-7b66578adb47
```

Affected products

github.com/0xJacky/Nginx-UI (Go) < 1.9.10-0.20260314152518-7b66578adb47, SEMVER:introduced=0,fixed=1.9.10-0.20260314152518-7b66578adb47
Nginxui Nginx Ui

Identifiers

CVE-2026-33031
GHSA-x234-x5vq-cc2v
GO-2026-5733

References

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.