A long-standing vulnerability in the HTTP/2 support of NGINX has been identified, which permits unauthorized code execution on affected servers. This significant flaw, tracked as CVE-2026-123007 and termed ‘nginx2root,’ has persisted since version 1.9.5, released back in September 2015. The flaw has now been addressed in versions 1.31.9 and 1.30.7, released today.
Details of the Vulnerability
F5, the company responsible for NGINX, has explained that the vulnerability allows attackers to execute code on servers where Address Space Layout Randomization (ASLR) is either disabled or bypassed. Security experts from Wiz demonstrated the flaw’s exploitation in environments where ASLR was circumvented. Similarly, Xint researchers managed to execute code using only an accessible HTTP/2 port.
The executed code gains the same permissions as an NGINX worker process. To escalate privileges to root level, another vulnerability must be exploited, as indicated by the Computer Incident Response Center Luxembourg (CIRCL). Xint’s testing revealed that, even within a Docker container, elevation to root was feasible through an additional bug found in the Linux kernel’s SCTP code.
Current Exploitation and Proof-of-Concept
As of now, there have been no reported incidents of this vulnerability being exploited in the wild, according to both the vendor and security researchers from Wiz and Rapid7. Likewise, the flaw is not listed in CISA’s Known Exploited Vulnerabilities catalog. Proof-of-concept code is available on GitHub; however, it is primarily intended for demonstrations on freshly initiated Docker containers on the same machine.
Every NGINX open-source version from 1.9.5 to 1.31.8 is susceptible, including recent versions from October 2023. The vulnerability also affects NGINX Plus versions R34 to R36, prior to the latest patches.
Mitigation and Fixes
F5 has released updates that fix the flaw in NGINX Open Source versions 1.31.9 and 1.30.7, and NGINX Plus versions 37.3.0.1 and 37.0.8.1. The updates also address four additional vulnerabilities with similar conditions to CVE-2026-123007, all rated 9.2 on the CVSS 4.0 scale.
Users are advised to fully restart NGINX after upgrading to ensure the new binaries are in use. Simply reloading the service may retain the older vulnerable processes. The official Docker images have been updated to reflect these changes.
Recommendations and Future Outlook
For immediate mitigation, CIRCL suggests disabling HTTP/2 until updates can be applied. This action mitigates the primary vulnerability and one related flaw but does not address all the issues. Additionally, blocking the SCTP kernel module is recommended for systems not utilizing SCTP.
Users should monitor for signs of exploitation, such as unexpected program starts by NGINX workers, abnormal exits, and unusual network activity. Keeping systems updated with the latest security patches remains critical in safeguarding against these types of vulnerabilities.
