Artificial intelligence has just revealed the presence of two critical flaws hidden within the NGINX server. Millions of websites could be affected and administrators must install patches urgently.
Several flaws hidden within the NGINX server for years
After the discovery of two critical security flaws threatening WordPress, five research teams have just uncovered security flaws hidden in the NGINX server, including that of Wiz. Some of them have been present on the server since 2015, almost 11 years.
Among the ten vulnerabilities revealed,two are classified as critical.Referenced CVE-2026-123633 and CVE-2026-123007, they have a rating of 9.2 out of 10 since they can allow a hacker to take remote control of a vulnerable NGINX server. By taking advantage of these flaws, a hacker could execute code on the server in question without having to identify himself. Administrators are therefore called upon to install patches urgently.
A server that runs millions of sites
Following the discovery of these flaws, the affected servers must be updated as soon as possible. F5, the parent company of NGINX, has just released a security update which fixes the 10 identified flaws.
If the alert is so important, it is because the server in question hosts hundreds of millions of websites around the world. More than 225 million sites would use NGINXbut not everyone is necessarily vulnerable. And since several services sometimes depend on a single installation, taking control of them can make it possible to steal sensitive data as well as to modify pages. Note that the two most critical flaws only concern servers where HTTP/2 is activated.
Flaws revealed thanks to AI
The Wiz team of researchers explained that they managed to uncover these flaws through the use of AI. These latter used Atlastheir AI code analysis platform. A tool that relies on the use of several models. The researchers explain that with such tools “complexity no longer constitutes an obstacle to the discovery or exploitation of these flaws”.
Although they indicate that these flaws are rather complicated to exploit, administrators should not wait to perform the update planned by NGINX. They must urgently upgrade to NGINX 1.30.7 or 1.31.9, depending on the branch used. If this is not possible, the researchers recommend disable HTTP/2 waiting for.

