NGINX and Java4Shell: Three critical vulnerabilities and the question of where these are running on your systems
NGINX: CVE-2026-123007, CVE-2026-123633 and others
There are several memory errors in NGINX’s HTTP/2 and HTTP/3 code. An attacker can exploit these to execute code without authentication, with the privileges of the web server process.
This does not automatically grant them root privileges on the host. To do so, they would need to chain the vulnerability with a separate flaw in the Linux kernel. However, this is no cause for complacency: the web server process has sufficient privileges to cause damage.
For CVE-2026-123007, an active HTTP/2 connection on an accessible listener is sufficient. An upstream server does not need to be configured. Consequently, even an NGINX instance that only serves static content is affected. The vulnerability dates back to version 1.9.5.
Rating: 9.2 according to CVSS 4.0. According to CVSS 3.1, the score is 8.1, as the attack is complex. There are no known instances of exploitation in the wild to date.
Java4Shell: CVE-2026-114938
Java4Shell is a memory corruption vulnerability in OpenJDK’s Base64 decoder. Base64 may sound like a niche topic, but it is present in a great many Java applications.
Affected are OpenJDK versions from 17.0.6 onwards on x86-64 CPUs with AVX-512 VBMI. This also applies to distributions such as Temurin, Corretto and Oracle Java SE. Systems running on ARM are not affected.
The researchers have demonstrated code execution without login on standard installations of Jira, Confluence, Jenkins, Keycloak, Artifactory and PingFederate. These are not obscure tools, but ones that run daily in many organisations.
What you should do now
These vulnerabilities should not be left unpatched until the next patch day.
NGINX
Update NGINX Open Source to 1.30.7 (Stable) or 1.31.9 (Mainline), NGINX Plus to 37.0.8.1 or 37.3.0.1.
Restart NGINX afterwards. A ‘reload’ command will not load the new version; the old code will continue to run.
If the update does not work straight away: disable HTTP/2 (http2 off;) and remove the QUIC listener for HTTP/3.
A note on checking the version: `nginx -v` often shows an old version due to backports in Linux distributions, even though the fix is already included. The version of the package in your distribution is what counts.
Java
Update your Java runtimes to the November builds from the respective vendor. Also bear in mind Java that comes bundled with applications and is not updated via the standard package manager.
The real problem is keeping track of everything
Applying the patches themselves is rarely the problem. The problem is the question that comes before it: where are NGINX and Java running, in which version, and which of these are connected to the internet?
NGINX often acts as a reverse proxy or ingress, sitting in front of many applications simultaneously. Java is embedded in applications, containers and tools that nobody has on their radar as a ‘Java system’. If you only patch the well-known servers here, you’ll quickly overlook that one container that’s been running unnoticed for two years.
This is where we provide support in collaboration with our partner Wiz. On request, we’ll scan your cloud environment directly for these vulnerabilities. You’ll receive:
all affected NGINX and Java instances,
a breakdown of which of these are accessible from the internet,
a patching sequence based on actual risk,
mitigation measures for systems you cannot patch immediately.
What our SOC contributes
Finding the vulnerability is only half the battle. The other half is detecting whether anyone has already exploited it. That’s why our Managed SOC builds detections for current incidents as soon as they become known.
This week we have:
added a detection that triggers when an NGINX process on a Linux system launches a shell or a download tool itself. A web server does not do this during normal operation, but typically does so following a successful exploit. This requires an EDR on the host.
built and rolled out a detection for a recent supply chain incident within a day.
We’ve expanded detection of enumeration tools such as LinPEAS and added GSocket, a tool attackers use to establish persistent access on Linux systems.
Wiz shows you the open door. Our SOC monitors what happens within the organisation afterwards.
Also on our radar
PHP: A critical security update has been announced for 19 November for all supported PHP versions, including one for CVE-2026-115560.
CVE-2026-90436: The vulnerability in Apache Axis 1.x is being actively exploited and is on the KEV list published by the US agency CISA. Affected systems include Confluence Data Centre and N-able N-central. Rating: 9.8 according to CVSS.
Quick answer
Is my NGINX affected if I’m not using HTTP/2? Not for CVE-2026-123007, as the vulnerability requires active HTTP/2 on an accessible listener. But also check HTTP/3: there are flaws there too. Without an update, the only solution is to remove the QUIC listener.
Is a ‘reload’ sufficient after the update? No. A ‘reload’ does not load the new program. NGINX must be restarted.
‘nginx -v’ shows an old version. Am I vulnerable? Not necessarily. Many Linux distributions apply the fix via a backport without changing the version number. The version of the package in your distribution is what matters.
Can an attacker gain root privileges via the NGINX vulnerabilities? Not directly. They run with the privileges of the web server process. They only gain root access if they additionally exploit a flaw in the Linux kernel.
Which Java systems are affected by Java4Shell? OpenJDK version 17.0.6 and later, and distributions based on it such as Temurin, Corretto and Oracle Java SE, provided they run on x86-64 CPUs with AVX-512 VBMI. ARM systems are not affected.
Are the vulnerabilities already being actively exploited? As of 19 November 2026, there are no known in-the-wild exploits for the NGINX vulnerabilities. CVE-2026-90436 in Apache Axis, on the other hand, is being actively exploited.
Want to know where you stand?
Get in touch. We’ll use Wiz to check which of your cloud systems are affected and tell you what to tackle first.
