Science & Tech · Cybersecurity · 1 hr ago
Critical NGINX flaws could let attackers run code on servers
F5 released fixes for serious flaws in NGINX, software that directs web traffic to websites and applications.
NGINX runs about a third of the world’s websites, and the flaws affect its open-source version and some NGINX Plus releases.
The most serious flaw can let attackers run code without logging in on a server with HTTP/2 enabled.
Researchers also showed that a separate Linux kernel flaw could be combined with an NGINX flaw to gain the highest level of access to a host machine.
AI-assisted research helped uncover several of the vulnerabilities, including one that had been in the code since 2015.
The attack demonstrations had specific requirements, and no attacks exploiting the flaws had been reported in the coverage.
Administrators should upgrade to a fixed release and fully restart NGINX so old worker processes stop running.
Researchers disclosed five exploitable flaws in NGINX, including one that can let an unauthenticated attacker run code on a server with HTTP/2 enabled.
The most severe flaw, CVE-2026-123007, is an integer underflow in NGINX’s HTTP/2 handling and has a CVSS score of 9.2 out of 10.
Researchers demonstrated chaining it with a separate Linux kernel flaw to gain root access to a host.
F5 released fixes for the five flaws, including NGINX Open Source versions 1.31.9 and 1.30.7.
The HTTP/2 exploit has practical limits, including a need for roughly 128 gigabytes of HTTP/2 traffic.
- Who
- Security researchers disclosed the flaws; F5, the company behind NGINX, released fixes.
- What
- Researchers found five exploitable NGINX flaws. The most severe can allow unauthenticated code execution when HTTP/2 is enabled.
- When
- The flaws were disclosed in November 2026. The Hacker News reported that fixes were released on November 18.
- Where
- In NGINX software running on servers, including setups with HTTP/2 enabled.
- Why
- An HTTP/2 credit-handling error can cause an integer underflow and an out-of-bounds memory operation.
This story does not have two clearly opposing sides.
NGINX version 1.9.5 was released, and the HTTP/2 flaw has been present since that version.
NGINX version 1.31.8 was released, and it was among the vulnerable versions.
The Hacker News reported the release of fixed NGINX versions 1.31.9 and 1.30.7.
- Flaws disclosed
- Five
- Most severe flaw
- CVE-2026-123007
- Severity score
- 9.2 out of 10 on CVSS
- Fixed Open Source versions
- 1.31.9 and 1.30.7
- Exploit traffic requirement
- Roughly 128 gigabytes of HTTP/2 traffic
3 sources
What people are saying
When we used Xint to scan NGINX, we didn’t know what to expect, since it’s a mature, widely deployed codebase that’s undergone years of scrutiny
We’re grateful for the collaboration with project maintainers to get a patch released quickly.