nginx2root: AI finds a 90-minute bug that hands attackers root on web servers
A flaw in nginx's HTTP/2 implementation can be chained with a Linux kernel bug to take over servers completely, even from inside Docker containers. The researchers say almost every publicly identifiable nginx server is affected. An AI found the bug in an hour and a half.

What's going on
Security researchers have published an attack chain called "nginx2root" that they say can be used to take over servers completely over the network. It starts with a vulnerability in nginx, one of the most widely used web servers in the world. nginx is the software that serves websites on countless machines or sits in front of other services as a reverse proxy. The bug is in its implementation of HTTP/2, the newer version of the protocol browsers and servers use to talk to each other.
The story spread partly through a post on the Chinese tech forum V2EX. The researchers have published a full write-up, including mitigations, on a dedicated site and in a blog post: nginx2root.com and xint.io/blog/nginx2root-remote-code-execution.
If you follow AI, here's the interesting part: the researchers say an AI found the nginx flaw after searching for only about 90 minutes.
How big is the problem?
The researchers say nginx versions 1.9.5 through 1.31.8 are affected. That's a huge range. Version 1.9.5 came out in 2015 and was the first release with the HTTP/2 module, so the bug has apparently been in nginx since HTTP/2 support arrived.
The researchers scanned publicly reachable servers whose nginx version can be identified from the outside. Many servers reveal their version number in the responses they send to browsers. By their count, 98.9 percent of these fall within the vulnerable range. The short description doesn't say how many of them can actually be attacked. That depends on things like whether HTTP/2 is enabled and whether the operating system also has the second vulnerability.
How the attack chain works
According to the write-up, the nginx flaw alone gives attackers remote code execution: they can run their own code on the server from anywhere on the network. At first, though, that code only runs with the privileges of the nginx process, and those are usually restricted on purpose.
To get full control, the researchers chained the bug with a second vulnerability, this time in the Linux kernel, the core of the operating system. The flaw is in the SCTP subsystem. SCTP (Stream Control Transmission Protocol) is a network protocol that moves data much like TCP does. It's used mostly in telecoms and is rarely needed on ordinary web servers. The kernel bug let the researchers carry out privilege escalation all the way to root, the Linux administrator account that can do anything.
The worrying part: in tests, the chain also broke out of Docker containers. Containers are isolated environments where programs run without direct access to the rest of the system. Think of a tenant who can only enter their own apartment. Many admins count on a compromised web server inside a container being unable to harm the host. But containers share the kernel with the host, so a kernel bug breaks that isolation. The researchers got root on the underlying machine.
The short report doesn't say which kernel versions are affected or whether either bug has an official identifier (a CVE number) yet.
The AI angle
The researchers say an AI tracked down the nginx flaw in 90 minutes, and that fits a trend. AI systems are increasingly used to comb through large codebases that have grown over many years, looking for security holes. nginx is a mature, heavily scrutinized open-source project. If a bug that went unnoticed there for about eleven years can be found that quickly, the balance of power is clearly shifting. The short report doesn't name the AI system or say how much human work went into building the full attack chain. The 90 minutes refers to finding the bug, not necessarily to building the whole chain.
What admins should do now
The researchers describe specific mitigations at nginx2root.com and on the xint.io blog. If you run nginx, read them. The usual advice for reports like this:
- Check your version: Run
nginx -vto see which version is installed. - Apply updates: Install fixes for nginx and the kernel as soon as the nginx developers and Linux distributions ship them. Reboot afterwards so the new kernel actually loads.
- Don't treat containers as your only layer of defense: The chain can escape Docker, so the host kernel needs to be up to date too.
- Turn off what you don't need: For workarounds, such as changes to HTTP/2 or the SCTP module, follow the researchers' own recommendations instead of guessing.
Our take
If the claims hold up, nginx2root is one of the most serious server vulnerabilities of the year. It hits an extremely widespread web server, it can be exploited over the network, and it ends in full root access, even across container boundaries. One caveat: the figures (98.9 percent, 90 minutes) come from the researchers themselves so far. The source contains no independent confirmation and no statements from the nginx developers or the kernel maintainers. A vulnerable version also doesn't automatically mean a vulnerable system, because an attack needs both bugs.
For the AI debate, this is one more sign that AI-assisted bug hunting now quickly finds flaws that humans missed for years. That helps defenders, but attackers have the same tools. For admins, the main lesson is to patch faster than before.
Sources
- V2EX 技术 (CN) v2ex.com
- Hatena Bookmark IT (JP) x.com
Ask the AI assistant
Questions about this article, installation or background? Our assistant knows this page and runs on our own machine, not in someone else's cloud.
The Assistant is an AI (Gemma 4) and can make mistakes – please check important details against the source. Questions are used only to generate an answer and are deleted after one hour. Please don't enter any personal data.
Comments
What do you think? Already tried it? Write it here, no sign-up needed.
Comments are public. Links aren't allowed, and we delete abusive posts. You can delete your own comment at any time in this browser. Learn more in the Privacy Policy.