CVE-2026-107810 json
Nginx UI: Backup restore follows crafted symlinks into the live Nginx configuration path before restore flags are applied
published last mo. modified 20d ago also EUVD-2026-95894 , GHSA-p8v3-89rh-jxc7 , GO-2026-6707
- cvss
- 8.1
- version 3.1, CNA
- cisa kev
- Not listed
- not in CISA's catalog
- epss
- 0.4%
- EPSS 0.4% chance of exploitation in 30 days, percentile 38%
- public exploits
- 0
- none known
Summary
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.
Patch / fix
- go github.com/0xJacky/Nginx-UI 1.9.10-0.20260728074146-a467ed652591
- nginxui nginx_ui 2.5.0
Is CVE-2026-107810 in your dependencies? Fencer shows which of your repositories are affected as soon as an advisory lands, and opens the fix as a pull request.
Check with FencerCISA SSVC
- Exploitation
- Proof of concept is public
- Automatable
- no
- Technical impact
- partial
- Assessed
- 27d ago
Exploit prediction
0.45% chance of exploitation in the next 30 days, higher than 38% of all scored CVEs (FIRST EPSS, 2026-11-09).
Exploits and checks
- github.com https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7 referenced PoC, tagged "exploit" by a source, unverified
CVSS scores
| assigned by | version | score | vector |
|---|---|---|---|
| CNA | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
| GitHub | 3.1 | 8.1 | CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/I:H/A:H |
Affected packages
| ecosystem | package | affected | fixed in |
|---|---|---|---|
| go | github.com/0xJacky/Nginx-UI | >=1.9.10-0.20250517140552-daee3ac7ade1, <1.9.10-0.20260728074146-a467ed652591 |
1.9.10-0.20260728074146-a467ed652591 |
Affected products
- 0xJacky nginx-ui
Classification
References
-
github.com
/0xJacky/nginx-ui/commit/a467ed652591fc0cd1b466a1ec751b493faef9f7
web, patch
-
github.com
/0xJacky/nginx-ui/security/advisories/GHSA-p8v3-89rh-jxc7
exploit, web, vendor-advisory, advisory
-
github.com
/0xJacky/nginx-ui/releases/tag/v2.5.0
web, release-notes
-
github.com
/0xJacky/nginx-ui
package
Sources
- CVE List CVE-2026-107810
- GitHub Advisory GHSA-p8v3-89rh-jxc7
- NVD CVE-2026-107810
- OSV GO-2026-6707
Fencer Intel keeps one entry per vulnerability: the CVE id wins, then GHSA, and records that alias each other are merged, except that two CVEs always keep separate entries. The same data is available as JSON.
CPEs and fixed versions use Anchore's correction of NVD's data: Added CPE configurations because not yet analyzed by NVD.