CVE-2026-84320 Nginx UI: Auto backup name allows path traversal outside validated storage path
An authenticated user can exploit path traversal in backup naming to write files outside the validated directory, potentially achieving code execution.
- Exploited in the wild
- Not known
- Login needed
- Any signed-in user
- Attackable
- Over the internet
- Victim action needed
- Not needed
- Fix
- Available
What is CVE-2026-84320?
CVE-2026-84320 is a medium-severity path traversal vulnerability in 0xJacky nginx-ui, published on 12 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim.
Official description
Nginx UI is a web user interface for the Nginx web server. Prior to 2.4.3, Nginx UI validates an automatic backup's storage_path, but AutoBackup.GetName returns a user-controlled name without rejecting path separators or parent-directory components, and downstream filename formatting embeds that result in the final archive filename. An authenticated user who can create or modify an automatic backup can cause filepath.Join to resolve the generated archive path outside the validated storage directory, allowing backup archives to be written with the Nginx UI process privileges. For encrypted configuration backups, the adjacent encryption key file can also be written outside the validated directory. This issue is fixed in version 2.4.3.
Weakness: CWE-22
Which versions are affected by CVE-2026-84320?
3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI.
| Package | Affected | Fixed in |
|---|---|---|
github.com/0xJacky/Nginx-UI Go | All versions | 1.9.10-0.20260715121709-f92218e01054 |
github.com/0xJacky/Nginx-UI Go | All versions | 1.9.10-0.20260715121709-f92218e01054 |
github.com/0xJacky/Nginx-UI Go | All versions | 1.9.10-0.20260715121709-f92218e01054 |
How do I fix CVE-2026-84320?
Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260715121709-f92218e01054 or later.
Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.
Is CVE-2026-84320 being exploited?
There is no known exploitation of CVE-2026-84320 in the wild and no public exploit code.
Sources
Also known as GHSA-jrq7-xrjx-pcfw, GO-2026-6788.