What A Time To Be Alive
Choose language: English

Two long-standing flaws in NGINX web server fixed, Wiz found them with AI

Two serious security flaws have been fixed in NGINX, software that keeps more than 225 million websites online. One had been in the code for over ten years. The security company Wiz found them with AI; updates have been available since 18 November 2026.

An old, rusty chain hangs horizontally in front of a blue-green background; in the middle, three links have been replaced by new, shiny silver ones. Below, in a beam of light, lies the old, broken link.
Replacing an old weak link: this is how the updates fix two flaws that sat in NGINX for years (illustrative photo, generated with AI)

F5, the company behind NGINX, released updates for two serious flaws in the software. NGINX is a web server: the program that receives requests from visitors and makes websites and apps reachable. According to Wiz, it runs on more than 225 million websites. Under certain conditions, the flaws let an attacker run their own code on a server without a password.

One of the two flaws had been in the code since a version from 2015, the other for almost six years. Five research teams found them independently of each other: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint.

Found with AI

The security company Wiz found both flaws with Wiz Atlas, the system behind its own AI scanner that searches program code for errors. To work out how serious the flaws were, the researchers used two AI models: Gemini 4 Carbon from Google and ChatGPT 5.6 Sol from OpenAI. Wiz reported the first flaw to F5 ; another team turned out to have reported it shortly before. The second report followed , two days before the updates.

What was wrong

Both flaws only work when HTTP/2 is switched on, a newer way for browsers and servers to talk to each other. In the first flaw (CVE-2026-123633), NGINX releases a piece of memory while a request is still using it. This mainly matters when NGINX passes traffic on to an application behind it, a common set-up. The second flaw (CVE-2026-123007) is a calculation error in controlling the amount of traffic, and can also occur when NGINX simply serves files.

Wiz gives both flaws a score of 9.2 on the international severity scale, which runs to 10, and calls them critical. NGINX itself rates them lower: the first as medium, the second as major.

What administrators can do

The flaws are in NGINX versions up to and including 1.31.8; the first from version 1.19.7, the second from 1.9.5. Versions 1.31.9 and 1.30.7 and newer are safe. Anyone who cannot update straight away can switch HTTP/2 off for the time being and then test whether everything still works.

Researcher Stephen Fewer of Rapid7 showed that the second flaw can really be exploited, and made his demonstration public. It is not easy: his attack sent about 128 gigabytes of traffic to the server and took two and a half minutes on a fast lab connection. Over a connection slower than about 300 megabits per second, it does not succeed within the hour that NGINX keeps a connection open by default. The attack also only works with a particular combination of processor and system software. According to Rapid7, other ways are possible, but none are known yet.

What does this mean for the road to the singularity?

An AI scanner finding flaws that went unnoticed for more than ten years in one of the most widely used programs on the internet shows how far these tools have come. They can follow complicated pieces of code that people missed when reviewing it. The more of these old flaws come to light now, the fewer are left for attackers.

At the same time, attackers use the same kind of AI. This week Google saw, for the first time, attackers using AI agents, programs that carry out tasks on their own with AI, that built an attack from a software update by themselves. That makes the speed at which administrators install updates more and more important. If updating also becomes largely automatic, the use of AI on both sides could in the end make internet software safer than ever: flaws would then be found and fixed faster than attackers can use them.

What is the technological singularity? Read the explanation →

Sources

  1. wiz.io
  2. Rapid7
  3. nginx.org