Critical NGINX vulnerabilities security alert showing server infrastructure at risk

Critical NGINX Vulnerabilities: nginx2root Security Alert

What Happened: Critical NGINX Security Flaws Exposed

Two critical NGINX vulnerabilities dubbed “nginx2root” could allow unauthenticated attackers to execute code remotely on vulnerable web servers, according to recent security research. Multiple research teams have demonstrated how these flaws can be chained with a Linux kernel bug to potentially gain root access to affected systems.

The vulnerabilities were discovered independently by researchers at Xint, Wiz, Ikotas Labs, Metnir, and Rapid7. Xint also discovered three additional NGINX remote code execution flaws. According to the report, Censys later reproduced the underlying memory corruption conditions in four of the five flaws through lab testing, but did not achieve remote code execution.

Source: BleepingComputer – Critical NGINX ‘NGINX2Root’ bugs let attackers hijack servers

How Do These NGINX Vulnerabilities Work?

The first nginx2root flaw is CVE-2026-123007, a flow-control bug that can corrupt memory in an NGINX worker. According to the report, it impacts all versions from 1.31.8 down to 1.9.5, released in 2015. Wiz demonstrated unauthenticated remote code execution on a server hosting ordinary static files over HTTP/2 with TLS.

Xint demonstrated root access by chaining CVE-2026-123007 with a separate Linux kernel flaw affecting the kernel’s SCTP subsystem. This combination could potentially be used to escape an NGINX Docker container and gain root privileges on the underlying host.

The Second Critical Flaw

The second vulnerability is CVE-2026-123633, a use-after-free problem affecting NGINX when it accepts HTTP/2 connections and proxies requests to a backend. It impacts all versions from 1.19.7 through 1.31.8. When the worker runs low on connection slots, it can close an active connection and free memory that a request still uses.

Wiz also demonstrated remote code execution via CVE-2026-123633. However, the firm is not publicly releasing its proof-of-concept exploits at this time.

Additional Vulnerabilities Patched

Three other flaws discovered by researchers and fixed by F5 include:

  • CVE-2026-121810 – Use-after-free affecting HTTP/3 reverse proxying
  • CVE-2026-123634 – Use-after-free affecting DNS resolution with subrequests
  • CVE-2026-113425 – Use-after-free affecting mail proxy authentication

F5’s security update also addresses CVE-2026-118899, a high-severity denial-of-service issue allowing an unauthenticated attacker to cause a worker to enter an infinite loop while reading a request body over TLS 1.3.

Evaluating the Real-World Risk

Security researcher Florian Roth commented that while these NGINX vulnerabilities are worse than Node2Shell and Java2Shell, they don’t appear to be an imminent threat for most deployments. According to the report, Roth noted the flaws are exploitable in non-default configurations, warning that claims of widespread exposure based solely on version numbers are misleading.

The two HTTP/2 flaws require:

  • An unpatched server
  • HTTP/2 enabled on a listener an attacker can reach
  • For CVE-2026-123633: NGINX must also proxy requests to a backend

According to Censys’ live exposure tracker, approximately 8.8 million NGINX services were potentially exposed to CVE-2026-123007 as of November 19, based on affected version numbers and HTTP/2 support. More than 511,000 previously exposed services have already been patched or mitigated. Another 104 million NGINX services do not disclose their versions, making exposure determination difficult.

What This Means for Australian Organisations

Note: This section provides general guidance and does not represent claims from the source material.

Australian organisations using NGINX should review their exposure as part of routine vulnerability management services. The ACSC Essential Eight emphasises patching applications as a critical mitigation strategy, and these critical vulnerabilities warrant immediate attention.

Organisations subject to the Security of Critical Infrastructure (SOCI) Act should assess whether their NGINX deployments fall within critical infrastructure assets requiring enhanced security measures. Implementing robust patch management processes aligns with both Essential Eight maturity and broader compliance obligations.

Actionable Recommendations for System Administrators

Based on the report’s guidance and security best practices, organisations should take these steps:

  1. Upgrade immediately to NGINX Open Source 1.30.7 stable or 1.31.9 mainline
  2. NGINX Plus users should update to versions 37.0.8.1 or 37.3.0.1
  3. Temporarily disable HTTP/2 if an immediate upgrade isn’t possible (note: this only mitigates the two nginx2root flaws)
  4. Review your configuration to determine actual exposure based on HTTP/2 enablement and backend proxying
  5. Monitor for indicators of compromise given demonstrated exploitation capability

Organisations requiring assistance with vulnerability assessment and remediation should consider engaging managed security services to ensure comprehensive coverage.

Frequently Asked Questions

What is the nginx2root vulnerability?

Nginx2root refers to two critical NGINX vulnerabilities (CVE-2026-123007 and CVE-2026-123633) that could allow unauthenticated attackers to execute code remotely on vulnerable web servers. When chained with a Linux kernel flaw, researchers demonstrated the potential to gain root access.

How can I protect my servers from these NGINX vulnerabilities?

Update to NGINX Open Source 1.30.7 stable or 1.31.9 mainline immediately. NGINX Plus users should update to versions 37.0.8.1 or 37.3.0.1. If you cannot upgrade immediately, temporarily disabling HTTP/2 provides partial mitigation for the two nginx2root flaws.

Are all NGINX servers affected by nginx2root?

Not all servers are equally at risk. According to the report, the flaws are exploitable in non-default configurations. Servers require HTTP/2 enabled and, for CVE-2026-123633, must also proxy requests to a backend. Many organisations may have already applied backported security fixes.

Key Takeaways

  • Two critical NGINX vulnerabilities could allow remote code execution on unpatched servers
  • Researchers demonstrated potential root access by chaining with a Linux kernel flaw
  • Approximately 8.8 million NGINX services potentially exposed based on version and HTTP/2 support
  • Patches are available in NGINX Open Source 1.30.7/1.31.9 and NGINX Plus 37.0.8.1/37.3.0.1
  • Actual exploitability depends on configuration, not just version numbers

Conclusion

These critical NGINX vulnerabilities represent a significant security concern for organisations running affected versions with HTTP/2 enabled. While the real-world exploitability depends on specific configurations, the demonstrated potential for root access through vulnerability chaining makes prompt patching essential.

System administrators should prioritise upgrading their NGINX installations and reviewing their security configurations. If your organisation needs assistance assessing exposure to these NGINX vulnerabilities or implementing a comprehensive patching strategy, speak with our security team today.

Related Reading

Tagged , , , , .