Is CVE-2026-107805 exploited in the wild?

No. Junglewise Threat Intelligence has no report of CVE-2026-107805 being exploited in the wild.

How severe is CVE-2026-107805?

High severity, with a CVSS score of 7.5, published 9 October 2026.

Which products and versions are affected?

0xJacky Nginx-UI 2.5.0 through 2.5.x; github.com/0xJacky/Nginx-UI (Go) >= 1.9.10-0.20260729084040-acb59fdd81db, < 1.9.10-0.20260901043436-8c9b9a1aff21, SEMVER:introduced=1.9.10-0.20260729084040-acb59fdd81db,fixed=1.9.10-0.20260901043436-8c9b9a1aff21.

Is there a fix for CVE-2026-107805?

Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260901043436-8c9b9a1aff21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

How is CVE-2026-107805 attacked?

It is attacked over the network, in a web application.

Am I affected by CVE-2026-107805?

Check whether you run 0xJacky Nginx-UI or github.com/0xJacky/Nginx-UI (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107805: Nginx UI unauthenticated denial of service via temporary storage exhaustion

Q: Is there a fix for CVE-2026-107805?

Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260901043436-8c9b9a1aff21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-107805 attacked?

It is attacked over the network, in a web application.

Q: Am I affected by CVE-2026-107805?

Check whether you run 0xJacky Nginx-UI or github.com/0xJacky/Nginx-UI (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

CVE-2026-107805 · Severity: high · CVSS 7.5 · Published 2026-10-09

Nginx UI is a management interface for the Nginx web server. Versions 2.5.0 through 2.5.x contain a flaw where unauthenticated attackers can send specially crafted requests that consume temporary disk storage and I/O resources before authentication is checked, potentially disrupting the service and others sharing the filesystem. The vulnerability does not allow attackers to bypass authentication or access sensitive data.

Technologies: 0xJacky Nginx-UI, github.com/0xJacky/Nginx-UI (Go). Vendors: 0xJacky, Go.

Quick answers

Is CVE-2026-107805 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107805 being exploited in the wild.
How severe is CVE-2026-107805?: High severity, with a CVSS score of 7.5, published 9 October 2026.
Which products and versions are affected?: 0xJacky Nginx-UI 2.5.0 through 2.5.x; github.com/0xJacky/Nginx-UI (Go) >= 1.9.10-0.20260729084040-acb59fdd81db, < 1.9.10-0.20260901043436-8c9b9a1aff21, SEMVER:introduced=1.9.10-0.20260729084040-acb59fdd81db,fixed=1.9.10-0.20260901043436-8c9b9a1aff21.
Is there a fix for CVE-2026-107805?: Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260901043436-8c9b9a1aff21 or later. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107805 attacked?: It is attacked over the network, in a web application.
Am I affected by CVE-2026-107805?: Check whether you run 0xJacky Nginx-UI or github.com/0xJacky/Nginx-UI (Go) at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.

How to fix

github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260901043436-8c9b9a1aff21 or later
```
go get github.com/0xJacky/Nginx-UI@v1.9.10-0.20260901043436-8c9b9a1aff21
```

Technical details

The vulnerability exists in the node-signature authentication path, which stages request bodies in temporary files and syncs them to disk before validating the cryptographic signature and body digest. An unauthenticated remote client can provide syntactically valid signature metadata without completing authentication, causing resource exhaustion. The flaw is triggered via network requests with no authentication required, and is fixed by validating signed metadata before body staging and enforcing streaming size limits.

Affected products

0xJacky Nginx UI 2.5.0 through 2.5.x

Identifiers

CVE-2026-107805
GHSA-j3hg-9rp3-5hw9
GO-2026-6734

Timeline

2026-09-30: disclosed
2026-10-09: advisory
2026-10-09: patched: Fixed in v2.6.0

References

https://api.github.com/users/lujiefsi

This page as Markdown. Free to reuse under CC BY 4.0 with a link back.