Is CVE-2026-107812 exploited in the wild?

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

How severe is CVE-2026-107812?

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

Which products and versions are affected?

github.com/0xJacky/Nginx-UI (Go) >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728114330-580585516dd8, SEMVER:introduced=1.9.10-0.20250517140552-daee3ac7ade1,fixed=1.9.10-0.20260728114330-580585516dd8; Uozi Nginx UI 2.3.11 and earlier.

How is CVE-2026-107812 attacked?

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

Am I affected by CVE-2026-107812?

Check whether you run github.com/0xJacky/Nginx-UI (Go) or Uozi Nginx UI 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-107812: Nginx UI unsigned binary self-upgrade allows RCE

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

Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260728114330-580585516dd8 or later. Until then: Reject HTTP URLs for the `github_proxy` setting and require HTTPS only. Treat `github_proxy` as a protected/restricted setting. Until a patch adding cryptographic signature verification is released, restrict access to the upgrade feature and monitor for unexpected process restarts or binary modifications on your system. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.

Q: How is CVE-2026-107812 attacked?

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

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

Check whether you run github.com/0xJacky/Nginx-UI (Go) or Uozi Nginx UI 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-107812 · Severity: high · CVSS 7.5 · Published 2026-10-09

Nginx UI is a web management interface for Nginx servers. When self-upgrading, the application downloads a new binary and verifies it only against a checksum from the same source, without cryptographic signature validation. An attacker who compromises the download mirror or performs a man-in-the-middle attack on cleartext HTTP can inject a malicious binary and matching checksum, achieving remote code execution as root when the upgrade is applied.

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

Quick answers

Is CVE-2026-107812 exploited in the wild?: No. Junglewise Threat Intelligence has no report of CVE-2026-107812 being exploited in the wild.
How severe is CVE-2026-107812?: High severity, with a CVSS score of 7.5, published 9 October 2026.
Which products and versions are affected?: github.com/0xJacky/Nginx-UI (Go) >= 1.9.10-0.20250517140552-daee3ac7ade1, < 1.9.10-0.20260728114330-580585516dd8, SEMVER:introduced=1.9.10-0.20250517140552-daee3ac7ade1,fixed=1.9.10-0.20260728114330-580585516dd8; Uozi Nginx UI 2.3.11 and earlier.
Is there a fix for CVE-2026-107812?: Yes. github.com/0xJacky/Nginx-UI (Go): upgrade to 1.9.10-0.20260728114330-580585516dd8 or later. Until then: Reject HTTP URLs for the `github_proxy` setting and require HTTPS only. Treat `github_proxy` as a protected/restricted setting. Until a patch adding cryptographic signature verification is released, restrict access to the upgrade feature and monitor for unexpected process restarts or binary modifications on your system. Junglewise finds every place you run it, drafts the upgrade and applies it once you approve.
How is CVE-2026-107812 attacked?: It is attacked over the network or from the adjacent network, in a web application.
Am I affected by CVE-2026-107812?: Check whether you run github.com/0xJacky/Nginx-UI (Go) or Uozi Nginx UI 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.20260728114330-580585516dd8 or later
```
go get github.com/0xJacky/Nginx-UI@v1.9.10-0.20260728114330-580585516dd8
```

Reject HTTP URLs for the `github_proxy` setting and require HTTPS only. Treat `github_proxy` as a protected/restricted setting. Until a patch adding cryptographic signature verification is released, restrict access to the upgrade feature and monitor for unexpected process restarts or binary modifications on your system.

Technical details

The vulnerability exists in the self-upgrade mechanism: both the release binary and its SHA-512 digest are downloaded from the same origin (default `cloud.nginxui.com` or a configured `github_proxy`), and integrity is verified only by comparing the digest to the binary's hash, with no cryptographic signature verification. The application accepts HTTP URLs for `github_proxy`, allowing cleartext downloads. A compromised mirror, DNS/BGP hijack, or on-path MITM attacker can serve a malicious binary with a matching digest, which passes validation and executes as root when the upgrade completes and the process restarts.

Affected products

uozi Nginx UI 2.3.11 and earlier

Identifiers

CVE-2026-107812
GHSA-662p-52hx-cmh2
GO-2026-6705

Timeline

2026-10-09: disclosed

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