Summary
nginx-ui has Race Condition that Leads to Persistent Data Corruption and Service Collapse
Impact
This is a High security risk (CWE-362: Race Condition).
- Integrity: Permanent corruption of application settings and system-level configuration.
- Availability: High. The attack results in a persistent Denial of Service that cannot be recovered via the web UI.
- Remote Code Execution (RCE) Risk: Since the application allows updating certain fields (like Node Name) and uses others as shell commands (like ReloadCmd or RestartCmd), the observed "cross-contamination" of INI values means an attacker could potentially force a user-controlled string into a command execution field. If ReloadCmd is overwritten with a malicious payload provided in another field, the next nginx reload will execute that payload. While highly impactful, this specific exploit path is non-deterministic and depends on the precise interleaving of thread execution, making targeted exploitation difficult.
Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing. Typical impact: TOCTOU exploits, data corruption, or privilege escalation.
Affected versions
Security releases
Kodem intelligence
Severity tells you how bad this could be in the worst case. It does not tell you whether you are exposed. Exploitability and impact are functions of runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A vulnerable package can sit in your dependency tree and never run.
Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter. Kodem's runtime-powered SCA identifies whether this CVE is reachable in your applications.
Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-33028? CVE-2026-33028 is a high-severity race condition vulnerability in github.com/0xJacky/Nginx-UI (go), affecting versions <= 1.99. It is fixed in 1.30.1. Multiple concurrent operations access a shared resource without proper synchronization, producing unpredictable results depending on timing.
- Which packages are affected by CVE-2026-33028?
github.com/0xJacky/Nginx-UI(go) (versions <= 1.99)github.com/uozi-tech/cosy(go) (versions <= 1.30.0)
- Is there a fix for CVE-2026-33028? Yes. CVE-2026-33028 is fixed in 1.30.1. Upgrade to this version or later.
- Is CVE-2026-33028 exploitable, and should I be worried? Whether CVE-2026-33028 is exploitable in your environment depends on whether the vulnerable code is present and reachable. A CVSS score is a worst-case rating; it does not account for your specific deployment, configuration, or usage patterns. Kodem, an Intelligent Application Security platform, uses runtime intelligence to show which vulnerabilities actually execute in production, so you can focus on the ones that represent real risk. Get a demo
- What actually determines whether CVE-2026-33028 is exploitable, and how bad it is? Exploitability and impact are not fixed properties of a CVE. They depend on runtime truth: whether the vulnerable code is present, reachable, and actually executes in your application. A high CVSS score on a dependency that never runs is not the same as real risk. Kodem, an Intelligent Application Security platform, uses runtime intelligence to reveal which vulnerabilities actually execute in production, so teams prioritize the ones that genuinely matter.
- How do I fix CVE-2026-33028? Upgrade
github.com/uozi-tech/cosyto 1.30.1 or later.