CVE-2026-107810 Nginx UI: Backup restore follows crafted symlinks into the live Nginx configuration path before restore flags are applied

High 8.1 Published Updated

Authenticated attackers can exploit symlink handling during backup restoration to modify live Nginx configuration files, potentially causing service disruption or unauthorized changes.

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-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, CWE-59

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.

PackageAffectedFixed in
github.com/0xJacky/Nginx-UI GoFrom 1.9.10-0.20250517140552-daee3ac7ade11.9.10-0.20260728074146-a467ed652591
github.com/0xJacky/Nginx-UI GoFrom 1.9.10-0.20250517140552-daee3ac7ade11.9.10-0.20260728074146-a467ed652591
github.com/0xJacky/Nginx-UI GoFrom 1.9.10-0.20250517140552-daee3ac7ade11.9.10-0.20260728074146-a467ed652591

Products include 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.

Upgrade, and resolve every user-supplied path against an allowed base folder before opening it. More about Path traversal.

Is CVE-2026-107810 being exploited?

It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107810 exists.

Sources

Also known as GHSA-p8v3-89rh-jxc7, GO-2026-6707.

Is CVE-2026-107810 in your software?

Upload an SBOM and sbomify checks it against every vulnerability here, every day.

Check your SBOMs for free