Summary
nginx-ui Backup Restore Allows Tampering with Encrypted Backups
Impact
An attacker capable of uploading or supplying a malicious backup can modify application configuration and internal state during restoration.
Potential impacts include:
- Persistent configuration tampering
- Backdoor insertion into nginx configuration
- Execution of attacker-controlled commands depending on configuration settings
- Full compromise of the nginx-ui instance
The severity depends on the restore permissions and deployment configuration.
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.
Already deployed Kodem?
See it in your environmentNew to Kodem? Get a demo →Remediation advice
Kodem Kai can prioritize this vulnerability in your dependency tree and generate a fix recommendation.
Frequently Asked Questions
- What is CVE-2026-33026? CVE-2026-33026 is a critical-severity security vulnerability in github.com/0xJacky/Nginx-UI (go), affecting versions < 1.9.10-0.20260315015203-f61bcec547c0. It is fixed in 1.9.10-0.20260315015203-f61bcec547c0.
- Which versions of github.com/0xJacky/Nginx-UI are affected by CVE-2026-33026? github.com/0xJacky/Nginx-UI (go) versions < 1.9.10-0.20260315015203-f61bcec547c0 is affected.
- Is there a fix for CVE-2026-33026? Yes. CVE-2026-33026 is fixed in 1.9.10-0.20260315015203-f61bcec547c0. Upgrade to this version or later.
- Is CVE-2026-33026 exploitable, and should I be worried? Whether CVE-2026-33026 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-33026 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-33026? Upgrade
github.com/0xJacky/Nginx-UIto 1.9.10-0.20260315015203-f61bcec547c0 or later.