The developers of nginx, the open-source web server and reverse proxy that sits in front of millions of websites, released emergency updates on 18 November 2026 that fix ten security flaws. Several of them can let an attacker who has no login run code on an exposed server, according to two security firms that found them, and both say the fixes should be installed as soon as possible.
The project's website lists nginx 1.30.7 (stable) and nginx 1.31.9 (mainline) as released on 18 November, with fixes for ten vulnerabilities. These include memory corruption in HTTP/2 flow control, use-after-free bugs in HTTP/2, HTTP/3, the DNS resolver and the mail proxy module, and a buffer overflow when alias is used with try_files.
The most serious bug has been there since 2015
Cloud security company Wiz said two of the flaws, tracked as CVE-2026-123633 and CVE-2026-123007, are rated critical with a CVSS 4.0 score of 9.2. Both need HTTP/2 to be switched on. Wiz said the second one, an integer underflow in HTTP/2 flow control, first appeared in nginx 1.9.5 in 2015 and can hit servers that only deliver static files, with no backend application or third-party module. Wiz added that standard memory protections such as ASLR do not stop these attacks.
Security firm Xint, which calls its findings "nginx2root", described five independent attack paths in nginx, covering HTTP/2, HTTP/3, the DNS resolver and the mail proxy. It said its researchers achieved remote code execution with the nginx worker's privileges in each case, testing against the official nginx 1.31.8 image. Xint said it also found a flaw in the Linux kernel's SCTP subsystem, introduced in 2018, that it chained with an nginx bug to gain root on the host, including from inside a Docker container. It said details of the kernel flaw are being withheld because no patch was available when it published.
AI tools helped find the flaws
Both firms said artificial intelligence played a role. Wiz said it found its two bugs using Wiz Atlas, the harness behind its AI code-scanning product, and used AI models to check their impact. Xint said one of its researchers found CVE-2026-123007 manually, and a fully automated Xint scan then found the other four nginx bugs without human guidance. Wiz said Ikotas Labs, Metnir, Rapid7 and Xint had also reported the issues independently to F5, the company behind nginx.
According to Wiz's timeline, it reported the first flaw to F5 on 21 October, received a patch for review on 10 November, and coordinated public disclosure with F5's security release on 18 November. Wiz said it built working exploits in its lab but will not publish them.
How many servers could be exposed
Xint said a Shodan search on 10 November returned 56.7 million hosts identifying as nginx. About 11.94 million of them showed a version number, and 98.9 per cent of those fell between 1.9.5 and 1.31.8, the range affected by the HTTP/2 flaw. Xint stressed that these are reported version strings, not confirmed vulnerable machines, because Linux distributions such as Ubuntu and Debian often backport fixes without changing the version number nginx reports.
What administrators should do
- Upgrade: both firms advise moving to the fixed releases, 1.30.7 or 1.31.9, or the matching patched package from a Linux distribution.
- Restart, not just reload: Xint said a reload alone does not replace the running program, so nginx should be restarted or upgraded live.
- Interim steps: where patching must wait, Wiz and Xint suggest turning off HTTP/2 on affected listeners, which Xint warned will break services that need it, such as gRPC. Xint also suggests disabling HTTP/3 listeners and restricting mail proxy listeners.
- Kernel: until a kernel fix arrives, Xint advises blocking the SCTP module on hosts that do not need it.
- Look for signs: both firms suggested checking for unexpected nginx worker crashes or commands launched by nginx. Xint warned that the HTTP/2 attack may leave little trace in access logs.
The disclosure comes the same day the US cybersecurity agency CISA urged organisations to "immediately patch" a separate Java flaw known as Java4Shell, according to CNBC.




