Hackerparagraph,IT-Security, Linux (Image © DALL-E)
Impact and Scope of the Vulnerability
The critical nature of these vulnerabilities stems from the fact that they lie within the NGINX core. Consequently, the server remains vulnerable even if the backend application’s code is secure. Since a single proxy often manages traffic for multiple services, a successful compromise of the NGINX instance could simultaneously grant an attacker access to various company services. The discovery of these vulnerabilities was the result of a collaboration among several research organizations, including Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint. Notably, the researchers used AI-powered analysis tools to identify these vulnerabilities.
Analysis of the Vulnerabilities
The two vulnerabilities offer different ways to compromise the server, both of which stem from how the software manages memory during active connections.
CVE-2026-123633: Connection Termination Bug
This vulnerability occurs when NGINX terminates a connection while a request is still being processed. The server frees the associated memory while the request continues to access it. An attacker can exploit this window of opportunity to quickly reallocate this memory and fill it with malicious content, thereby gradually gaining control of the server. This exploit is particularly effective when NGINX is running as a proxy.
CVE-2026-123007: HTTP/2 Flow Control Flaw
This vulnerability lies in the mechanism for controlling HTTP/2 data flow, which regulates the volume of data transmitted by NGINX. By manipulating data transmission and intentionally interrupting the connection, an attacker can corrupt the internal counters. This causes the program to read from and write to memory areas outside the intended boundaries. Investigations have revealed that this specific vulnerability has been present in the source code since version 1.9.5, which was released in 2015.
Remediation and Patch Management
F5 released security updates on November 18, 2026, to address these vulnerabilities. The affected versions and corresponding fixes are listed below:
Affected Versions:
- NGINX Open Source: Versions 1.19.7 and later (for CVE-2026-123633) and 1.9.5 and later (for CVE-2026-123007).
- NGINX Plus: Versions R33 and 37.0.0.
Fixed Versions:
- Stable branch: Version 1.30.7
- Mainline branch: Version 1.31.9
- NGINX Plus: Versions 37.0.7.1, 37.2.0.1, 37.0.8.1, or 37.3.0.1, depending on the specific vulnerability being addressed.
Temporary Workaround:
Administrators who cannot install patches immediately are advised to disable HTTP/2 support, provided that the application’s compatibility with HTTP/1.1 has been verified.
Disclosure Timeline
These disclosures were coordinated according to a strict timeline. F5 was first notified of CVE-2026-123633 on October 21, 2026. The second report regarding CVE-2026-123007 followed on November 16, just one day before the coordinated public announcement on November 18. To date, no public proof-of-concept exploits have been released.
