# CVE-2026-107805: Nginx UI: Unauthenticated signed-request body staging can exhaust temporary storage

> Unauthenticated attackers can exhaust temporary storage and resources in Nginx UI by sending signed requests with large bodies before validation.

- **Severity:** High 7.5 (`CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 9 Oct 2026
- **Updated:** 13 Oct 2026
- **Also known as:** GHSA-j3hg-9rp3-5hw9, GO-2026-6734

## What is CVE-2026-107805?

CVE-2026-107805 is a high-severity denial of service vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official description

Nginx UI is a web user interface for the Nginx web server. From 2.5.0 until 2.6.0, the node-signature authentication path performs temporary file staging of an attacker-controlled request body and synchronizes it before validating the body digest and cryptographic signature. An unauthenticated remote client that can reach the API and provide syntactically valid signature metadata can consume temporary filesystem capacity, disk input and output, and request-processing resources before rejection. The issue affects availability and does not bypass authentication or provide confidentiality or integrity impact. This issue is fixed in version 2.6.0.

Weakness: CWE-400 (Uncontrolled Resource Consumption)

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

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.20260729084040-acb59fdd81db | 1.9.10-0.20260901043436-8c9b9a1aff21 |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20260729084040-acb59fdd81db | 1.9.10-0.20260901043436-8c9b9a1aff21 |
| `github.com/0xJacky/Nginx-UI` | Go | From 1.9.10-0.20260729084040-acb59fdd81db | 1.9.10-0.20260901043436-8c9b9a1aff21 |

Products: Nginxui Nginx Ui.

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

Upgrade github.com/0xJacky/Nginx-UI to 1.9.10-0.20260901043436-8c9b9a1aff21 or later.

## Is CVE-2026-107805 being exploited?

There is no known exploitation of CVE-2026-107805 in the wild and no public exploit code.

## 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-107805 and fix it if it is affected.

What it is: CVE-2026-107805 is a high-severity denial of service vulnerability in 0xJacky nginx-ui, published on 9 Oct 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-107805 in the wild and no public exploit code.

Affected packages and fixed versions:
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260729084040-acb59fdd81db; fixed in 1.9.10-0.20260901043436-8c9b9a1aff21
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260729084040-acb59fdd81db; fixed in 1.9.10-0.20260901043436-8c9b9a1aff21
- github.com/0xJacky/Nginx-UI (Go): affected from 1.9.10-0.20260729084040-acb59fdd81db; fixed in 1.9.10-0.20260901043436-8c9b9a1aff21

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-107805/ (Markdown: https://insights.sbomify.com/CVE-2026-107805/index.md)
```

## Sources

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

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