# CVE-2026-107810: Nginx UI: Backup restore follows crafted symlinks into the live Nginx configuration path before restore flags are applied > Authenticated attackers can exploit symlink handling during backup restoration to modify live Nginx configuration files, potentially causing service disruption or unauthorized changes. - **Severity:** High 8.1 (`CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H`) - **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:** 9 Oct 2026 - **Updated:** 13 Oct 2026 - **Also known as:** GHSA-p8v3-89rh-jxc7, GO-2026-6707 ## What is CVE-2026-107810? CVE-2026-107810 is a high-severity path traversal vulnerability in 0xJacky nginx-ui, published on 9 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. From 2.0.0 until 2.5.0, internal/backup/restore.go extracts inner archives before applying the restore_nginx and restore_nginx_ui flags and permits symlinks targeting the live Nginx configuration path. An authenticated user who can create and restore backups can craft a valid backup that places a symlink in the staging tree and then writes a regular file through that link, even when both restore flags are false. This can persistently inject configuration or cause denial of service when the modified files are later consumed. This issue is fixed in version 2.5.0. Weakness: CWE-61 (UNIX Symbolic Link (Symlink) Following), CWE-59 (Improper Link Resolution Before File Access) ## Which versions are affected by CVE-2026-107810? 3 open source packages ship an affected version, including github.com/0xJacky/Nginx-UI. It affects 1 product. | Package | Ecosystem | Affected | Fixed in | | --- | --- | --- | --- | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074146-a467ed652591 | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074146-a467ed652591 | | `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20250517140552-daee3ac7ade1 | 1.9.10-0.20260728074146-a467ed652591 | Products: Nginxui Nginx Ui. ## How do I fix CVE-2026-107810? Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074146-a467ed652591 or later. ## Is CVE-2026-107810 being exploited? It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107810 exists. ## Other vulnerabilities in 0xJacky nginx-ui - [CVE-2026-33032](https://insights.sbomify.com/CVE-2026-33032/): Nginx UI: Unauthenticated MCP Endpoint Allows Remote Nginx Takeover (critical 9.8) - [CVE-2026-27944](https://insights.sbomify.com/CVE-2026-27944/): Nginx UI: Unauthenticated Backup Download with Encryption Key Disclosure (critical 9.8) - [CVE-2024-23827](https://insights.sbomify.com/CVE-2024-23827/): Nginx-UI arbitrary file write through the Import Certificate feature (critical 9.8) - [CVE-2026-107806](https://insights.sbomify.com/CVE-2026-107806/): Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite (critical 9.4) - [CVE-2026-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4) ## Fix prompt for AI coding agents ```text Check this codebase for CVE-2026-107810 and fix it if it is affected. What it is: CVE-2026-107810 is a high-severity path traversal vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. Any signed-in user can exploit it over the network, with no action from the victim. Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107810 exists. Affected packages and fixed versions: - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074146-a467ed652591 - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074146-a467ed652591 - github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20250517140552-daee3ac7ade1; fixed in 1.9.10-0.20260728074146-a467ed652591 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-107810/ (Markdown: https://insights.sbomify.com/CVE-2026-107810/index.md) ``` ## Sources - CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107810 - NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107810 - OSV: https://osv.dev/vulnerability/CVE-2026-107810 --- From sbomify Insights: https://insights.sbomify.com/CVE-2026-107810/ Summaries are generated and may contain mistakes; the official description above is the record.