Critical NGINX HTTP/2 Flaws Trigger Global RCE Alert: Millions of Servers at Risk
A massive cybersecurity alarm has been triggered. Two critical vulnerabilities in NGINX—the world's most widely used open-source web server—could allow unauthenticated attackers to execute malicious code and take control of millions of servers worldwide.
NGINX acts as the "front door" for modern web architectures. It powers more than 225 million websites, handling HTTPS and routing incoming traffic to the right application or API. Because it manages traffic for multiple applications simultaneously, a single compromised NGINX deployment can put hundreds of internal services and sensitive databases at risk.
The vulnerabilities, tracked as CVE-2026-123633 and CVE-2026-123007, are both rated critical with a CVSS 4.0 score of 9.2. They are memory-safety flaws residing directly within NGINX itself. This means that even if the website or API behind the NGINX server has perfectly secure code, it remains highly vulnerable.
Both vulnerabilities require HTTP/2 to be enabled on the affected NGINX server. Shockingly, CVE-2026-123007 affects versions dating all the way back to NGINX 1.9.5, released in 2015. The flaw has been hiding in plain sight for over a decade.
Anatomy of the NGINX Flaws
Security researchers independently uncovered these bugs while analyzing how NGINX processes HTTP/2 traffic.
- CVE-2026-123633 (Use-After-Free): This flaw occurs when a connection's memory is freed by NGINX while a request still needs it. Under specific conditions, when available connection slots run low, an attacker can force the server to process a request using memory that has already been reallocated, leading to Remote Code Execution (RCE).
- CVE-2026-123007 (Integer Underflow): This bug stems from incorrect flow-control accounting. A client can manipulate the `send_window` counter, pushing it past its maximum limit. This results in a massive underflow, tricking NGINX into executing an out-of-bounds memory copy. Researchers successfully demonstrated code execution on NGINX serving ordinary static files without any backend application.
The Role of AI: Dissolving the Complexity Barrier
What makes the discovery of these flaws particularly striking is how they were found. Historically, memory-safety flaws like these were incredibly difficult to trace because they require analyzing subtle interactions between memory operations and multiple code paths. For years, this complexity was a natural barrier against exploitation.
However, AI is fundamentally dissolving that barrier. Researchers utilized advanced AI models to scan the codebase, successfully uncovering vulnerabilities that had been hidden for nearly a decade. The same AI capabilities that help defenders uncover flaws can also help attackers investigate them. The window between vulnerability disclosure and active exploitation is shrinking drastically—from days to mere hours.
Urgent Mitigation and Patching Guidance
F5, the company behind NGINX, has released security patches to address these severe flaws. Organizations must immediately identify affected deployments and upgrade their systems. The fixed releases are:
- NGINX Open Source: Upgrade to 1.30.7 (stable) or 1.31.9 (mainline).
- NGINX Plus: Upgrade to 37.0.7.1, 37.2.0.1, 37.0.8.1, or 37.3.0.1 depending on your branch.
If you cannot upgrade immediately: You must temporarily disable HTTP/2 on affected NGINX instances. You can do this by setting http2 off; in the affected server blocks (for NGINX 1.25.1 or later) and removing the http2 parameter from any listen directives. Test application compatibility, reload NGINX, and confirm that the old worker processes have exited.
The Bottom Line
The discovery of these critical NGINX flaws is a stark reminder of the fragility of the open-source infrastructure that powers the internet. Complexity can no longer be relied upon as a shield against discovery. As AI models become more advanced, long-standing vulnerabilities that were once considered practically unreachable will be exposed at an unprecedented rate. Security teams must transition to a proactive posture: prioritize external-facing assets, maintain rigorous patch management, and continuously monitor for anomalous traffic patterns that could indicate an attempted exploitation.
Artikel Terverifikasi
Artikel ini terdaftar resmi di Data Cyber Indonesia.
DCY-ART-2026-316
Verifikasi keaslian →