# CVE-2026-107806: Nginx UI: Authenticated Remote Code Execution via Backup Restore App Config Overwrite

> An authenticated administrator can achieve remote code execution by uploading a malicious backup that overwrites application configuration files.

- **Severity:** Critical 9.4 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:H/UI:N/VC:H/VI:H/VA:H/SC:H/SI:H/SA:H`)
- **Exploited in the wild:** Not known
- **Login needed:** An administrator
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 14 Oct 2026
- **Also known as:** GHSA-p393-cf76-4jmr, GO-2026-6741

## What is CVE-2026-107806?

CVE-2026-107806 is a critical code injection vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.

### Official description

Nginx UI is a web user interface for the Nginx web server. From 2.3.8 until 2.5.0, an authenticated administrator with an active secure session can submit attacker-controlled portable backup key material and a matching manifest to POST /api/restore. The restore flow trusts the supplied key, decrypts attacker-controlled contents, and replaces the live app.ini, including protected nginx command settings such as TestConfigCmd. Triggering POST /api/nginx/test then executes the restored command in the Nginx UI runtime context, affecting confidentiality, integrity, and availability. This issue is fixed in version 2.5.0.

Weakness: CWE-94 (Improper Control of Generation of Code)

## Which versions are affected by CVE-2026-107806?

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.20260421071512-7864e378f5cf | 1.9.10-0.20260728074146-a467ed652591 |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20260421071512-7864e378f5cf | 1.9.10-0.20260728074146-a467ed652591 |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20260421071512-7864e378f5cf | 1.9.10-0.20260728074146-a467ed652591 |

Products: Nginxui Nginx Ui.

## How do I fix CVE-2026-107806?

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260728074146-a467ed652591 or later.

## Is CVE-2026-107806 being exploited?

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

Public exploit code:

- CVE-2026-107806 — nginx-ui 2.3.8–2.4.x auth RCE via forged backup restore (TestConfigCmd). PoCbit PoC: GET /api/backup, tamper app.ini, POST /api/restore, POST /api/nginx/test. check/exploit, batch url|JWT. Fixed 2.5.0. https://pocbit.org/pocs/cve-2026-107806 (github_poc): https://github.com/murrez/CVE-2026-107806

## 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-33026](https://insights.sbomify.com/CVE-2026-33026/): nginx-ui Backup Restore Allows Tampering with Encrypted Backups (critical 9.4)
- [CVE-2026-42238](https://insights.sbomify.com/CVE-2026-42238/): Unauthenticated Remote Code Execution via Backup Restore in nginx-ui (critical 9.0)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-107806 and fix it if it is affected.

What it is: CVE-2026-107806 is a critical code injection vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. An attacker needs administrator access to exploit it, with no action from the victim.
Exploitation: It is not confirmed as exploited in the wild, but public exploit code for CVE-2026-107806 exists.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260421071512-7864e378f5cf; fixed in 1.9.10-0.20260728074146-a467ed652591
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260421071512-7864e378f5cf; fixed in 1.9.10-0.20260728074146-a467ed652591
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260421071512-7864e378f5cf; 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-107806/ (Markdown: https://insights.sbomify.com/CVE-2026-107806/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-107806
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-107806
- OSV: https://osv.dev/vulnerability/CVE-2026-107806

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-107806/
Summaries are generated and may contain mistakes; the official description above is the record.