Nginx UI: Auto backup name allows path traversal outside validated storage path
CVE-2026-84320GHSA-jrq7-xrjx-pcfw
What to do
Vendor fix available. Upgrade each affected package to the fixed version on its release line (github.com/0xJacky/Nginx-UI 1.9.10-0.20260715121709-f92218e01054), redeploy, then verify what is actually installed.
This page has no inventory attached, so it cannot say whether you are affected. A vendor fix is not proof that your deployment is fixed.
Affected packages
Go github.com/0xJacky/Nginx-UI
- Affected
- < 1.9.10-0.20260715121709-f92218e01054
- Fixed in
- 1.9.10-0.20260715121709-f92218e01054
Sources
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GO-2026-6788 lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054 (fixed)
VerifiedObserved Structured OSV record; not marked as GitHub-reviewed.
- Open Source Vulnerabilities (OSV.dev), including the GitHub Advisory Database
OSV record GHSA-jrq7-xrjx-pcfw lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054 (fixed)
VerifiedObserved Structured OSV record; GitHub-reviewed advisory.
- GitHub Advisory Database and maintainer security advisories on GitHub
GitHub-reviewed advisory GHSA-jrq7-xrjx-pcfw lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054
VerifiedObserved Structured GitHub Advisory Database record (type=reviewed) from the GitHub REST API.
Severity and exploitation
- Exploitation
- No confirmed exploitation recorded. Patch Next marks exploitation only from CISA KEV.
- CVSS
- 6.3 · CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:L/I:L/A:L
- EPSS
- CVE-2026-84320: 0.17% estimated exploitation activity in the next 30 days; percentile 6.03 (FIRST EPSS, 2026-11-03). This is a model estimate, not proof of exploitation or customer exposure.
Source description
As published by the source; long descriptions are shortened.
Summary Nginx UI validates backuppath and storagepath against the administrator-defined backup.GrantedAccessPath boundary, but the final auto-backup output filename is built from the user-controlled auto-backup name without stripping path separators or .. components. An authenticated user who can create or modify an auto-backup task can set a name such as task/../../../escaped. The configured storagepath still passes validation because it is inside GrantedAccessPath, but the generated backup path escapes that storage directory when filepath.Join(storagepath, filename) resolves the embedded traversal sequence. This bypasses the documented backup path boundary and allows backup archives, and for encrypted configuration backups the adjacent .key file, to be written outside the intended storage directory with the Nginx UI process privileges. Affected Versions - Current dev branch commit checked: 4948fba8744e82c3d7003f68ee164e9f49421066 - Latest release checked: v2.3.10, published…
Dates and revisions
- Published by the source
- Last modified by the source
- Source last checked
- Revision 3 · amended ·
Amended from ghsa record GHSA-jrq7-xrjx-pcfw
- Revision 2 · amended ·
Amended from osv record GO-2026-6788
- Revision 1 · created ·
Published from osv record GHSA-jrq7-xrjx-pcfw
Agent brief
Preview the exact text before you copy it. Commands are read-only suggestions; review them before running anything.
# Patch Next advisory brief: CVE-2026-84320 Advisory: Nginx UI: Auto backup name allows path traversal outside validated storage path IDs: CVE-2026-84320, GHSA-jrq7-xrjx-pcfw Record: https://patchnext.com/advisories/cve-2026-84320 (revision 3, source checked 26 Oct 2026, 15:32 UTC) Inventory: none attached. This brief comes from a public page and does not say whether any deployment is affected. Severity: Medium (CVSS 6.3) Exploitation: no confirmed exploitation recorded. Patch Next confirms exploitation only from CISA KEV. Vendor response: Vendor fix available; fixed versions by package: github.com/0xJacky/Nginx-UI 1.9.10-0.20260715121709-f92218e01054. A vendor fix does not mean a deployment is fixed. ## Affected components - Go github.com/0xJacky/Nginx-UI: affected < 1.9.10-0.20260715121709-f92218e01054; fixed in 1.9.10-0.20260715121709-f92218e01054 ## Suggested inspection (read-only) - Go github.com/0xJacky/Nginx-UI: check the installed version with your package manager. ## Supported action Upgrade each affected component to a fixed version on its release line. For a transitive dependency, upgrade the parent package or add an override or constraint, then regenerate the lockfile. Redeploy every environment that ran an affected version. ## Required regression checks - Run the test suite and a production build. - Exercise the features that depend on github.com/0xJacky/Nginx-UI. - Repeat the inspection and confirm that only fixed versions remain installed. ## Rollback considerations - Keep the previous lockfile and deployment artifact. Rolling back reinstates the vulnerable version, so apply any documented mitigation while you fix forward. ## Unresolved questions - Which deployments run an affected version? - Exploitation status can change. Check again before lowering the priority. - Mark the work resolved only after the fixed version is verified in production. ## Sources - Verified: https://osv.dev/vulnerability/GO-2026-6788 (OSV record GO-2026-6788 lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054 (fixed)) - Verified: https://osv.dev/vulnerability/GHSA-jrq7-xrjx-pcfw (OSV record GHSA-jrq7-xrjx-pcfw lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054 (fixed)) - Verified: https://github.com/advisories/GHSA-jrq7-xrjx-pcfw (GitHub-reviewed advisory GHSA-jrq7-xrjx-pcfw lists affected ranges: Go github.com/0xJacky/Nginx-UI >=0 <1.9.10-0.20260715121709-f92218e01054) Commands are suggestions: review each one before running it.
Loading voting…