# 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.

- **Severity:** Medium 6.3 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L`)
- **Exploited in the wild:** Not known
- **Login needed:** Any signed-in user
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 12 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-jrq7-xrjx-pcfw, GO-2026-6788

## 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 (Improper Limitation of a Pathname to a Restricted Directory)

## Which versions are affected by CVE-2026-84320?

3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI.


| Package | Ecosystem | 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.

## Is CVE-2026-84320 being exploited?

There is no known exploitation of CVE-2026-84320 in the wild and no public exploit code.

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-84320 and fix it if it is affected.

What it is: 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.
Exploitation: There is no known exploitation of CVE-2026-84320 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20260715121709-f92218e01054
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20260715121709-f92218e01054
- github.com/0xJacky/Nginx-UI (Go): affected all versions; fixed in 1.9.10-0.20260715121709-f92218e01054

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-84320/ (Markdown: https://insights.sbomify.com/CVE-2026-84320/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-84320
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-84320
- OSV: https://osv.dev/vulnerability/CVE-2026-84320

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-84320/
Summaries are generated and may contain mistakes; the official description above is the record.