Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite

github.com/0xJacky/Nginx-UI (go)

## Summary An authenticated nginx-ui user can call `POST /api/restore`, upload a forged encrypted backup, restore `app.ini`, set nginx command settings such as `TestConfigCmd`, and then trigger command execution with `POST /api/nginx/test`. This was validated on nginx-ui `2.3.11 2(523) 6c86e5a5` in the local Docker container `uozi/nginx-ui:latest`. ##…

First seen: 9 Oct 2026
Last update: 9 Oct 2026, 20:45 UTC
Fixed in: github.com/0xJacky/Nginx-UI 1.9.10-0.20260728074146-a467ed652591
Identifiers: CVE-2026-107806
CVSS: 9.4
Source: GitHub advisory
On the menu as: Go
nginx

Check this repository for exposure to one security incident from pwned.coffee. Report first, change nothing until I say so.

## Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite
Severity: critical. Patch status: patched.
Affected: github.com/0xJacky/Nginx-UI (go)
Fixed in: github.com/0xJacky/Nginx-UI 1.9.10-0.20260728074146-a467ed652591
Ids: CVE-2026-107806

## Summary An authenticated nginx-ui user can call `POST /api/restore`, upload a forged encrypted backup, restore `app.ini`, set nginx command settings such as `TestConfigCmd`, and then trigger command execution with `POST /api/nginx/test`. This was validated on nginx-ui `2.3.11 2(523) 6c86e5a5` in the local Docker container `uozi/nginx-ui:latest`. ##…

## Steps
1. Search every lockfile and manifest (package-lock.json, yarn.lock, pnpm-lock.yaml, requirements*.txt, poetry.lock, uv.lock, composer.lock, go.sum, Cargo.lock, Gemfile.lock) for `github.com/0xJacky/Nginx-UI`. For each hit, compare the installed version with the fix on the same major line: github.com/0xJacky/Nginx-UI 1.9.10-0.20260728074146-a467ed652591. If it's lower, give the exact upgrade command for the package manager this repo uses.
2. This touches infrastructure (nginx). Look in terraform, ansible, cloud-init, Dockerfiles and docs for the product and version we run. If it isn't in the repo, say so and list what a human should check on the box.

## Report
A table: file, product or package, version in use, affected yes/no, exact fix. Then anything a human has to check outside the repo.

If you have the pwned.coffee MCP server (https://pwned.coffee/mcp), call lookup_cve("CVE-2026-107806") for the latest, and check_repo with this repo's lockfiles, Dockerfiles and workflows for a full receipt.
Sources: https://github.com/0xJacky/nginx-ui/commit/a467ed652591fc0cd1b466a1ec751b493faef9f7 https://github.com/0xJacky/nginx-ui/releases/tag/v2.5.0 https://github.com/0xJacky/nginx-ui/security/advisories/GHSA-p393-cf76-4jmr https://github.com/advisories/GHSA-p393-cf76-4jmr https://nvd.nist.gov/vuln/detail/CVE-2026-107806
https://pwned.coffee/i/nginx-ui-authenticated-remote-code-execution-via-backup-cve-2026-107806

Sources

Totalone very hot coffee