Security Update: NGINX and Java Vulnerabilities (November 2026)

In November 2026 two sets of vulnerabilities were published: critical flaws in NGINX, known as nginx2root, and a flaw in Java known as Java4Shell. This page explains what they are, which parts of your Cloud UniFi service they touch, and what we have done.


At a glance

Service Java4Shell nginx2root
UniFi Network Application Cannot be reached on our servers Not affected, does not use NGINX
UniFi OS Server Cannot be reached on our servers Mitigated, Ubiquiti's fix to follow
UISP Not affected, does not use Java Mitigated, Ubiquiti's fix to follow

What nginx2root is

On 18 November 2026 F5, the company behind NGINX, released fixes for ten vulnerabilities in NGINX, a web server used inside many products. Five of them are rated critical and are known together as nginx2root: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. The fixes are in NGINX 1.30.7 and 1.31.9.

The two that matter most, CVE-2026-123007 and CVE-2026-123633, are in the way NGINX handles HTTP/2, and can let an attacker run code on a server without logging in. The other three critical ones need NGINX features that UniFi OS Server and UISP do not use: HTTP/3, the mail proxy, and request mirroring or server-side includes.

What Java4Shell is

On 17 November 2026 new Java releases (17.0.21.1, 21.0.13.1 and 25.0.5.1) fixed a flaw reported as CVE-2026-114938 and nicknamed Java4Shell. The flaw is in code that Java uses only on processors with a particular set of instructions, called AVX-512.

How this affects your service

UniFi Network Application and UniFi OS Server: Java

Both run on Java. The servers that host them for our customers do not have AVX-512, so Java never uses the affected code and the flaw cannot be reached. We checked every one of our hosting servers on 19 November 2026.

Where a UniFi service runs on a server of its own that does have AVX-512, we installed the fixed Java version and restarted the service on 19 November 2026. We will install the fixed Java version everywhere else in our routine updates.

UniFi OS Server and UISP: NGINX

UniFi OS Server and UISP each include their own copy of NGINX, built by Ubiquiti, so only an update from Ubiquiti can replace it.

On our hosting servers nobody connects to that copy of NGINX directly. Every connection first reaches our own proxy, which handles HTTP/2 itself and passes each request on to NGINX over a separate connection of its own. The published attack depends on the attacker's own HTTP/2 traffic reaching NGINX, and our proxy does not pass it through.

Where a UISP service runs on a server of its own, without that proxy, we switched HTTP/2 off on 19 November 2026. Browsers and UISP devices work as before.

When Ubiquiti releases versions of UniFi OS Server and UISP with a fixed NGINX, we will install them on our own test services first, then on yours, and update this page.

What we checked and found

On 19 November 2026 we checked the NGINX logs of every UniFi OS Server and UISP service we host for the sign these attacks leave behind: NGINX worker processes crashing. We found none.

Questions and answers

Do I need to do anything?

No. Everything described on this page happens on our side.

Will I notice any change?

No. Your controller, your devices and your UISP service work exactly as before.

Should I change my passwords?

We found no sign of these vulnerabilities being used against your service, so this is not required. If you prefer to be cautious, changing your administrator passwords does no harm.

Are the UniFi devices on my sites affected?

Not through our service. A UniFi console you run on site, such as a Dream Machine or a Cloud Key, is separate from your Cloud UniFi service and is updated by you. Keep its management page off the internet and install Ubiquiti's updates for it when they are released. These consoles use ARM processors, which Java4Shell does not affect.

Where can I read more?

F5 lists the NGINX vulnerabilities and fixed versions in its security notice of 18 November 2026. The Java flaw is tracked as CVE-2026-114938.

How to contact us

Use the chat in your customer portal or email [email protected]. Please include your hostname.