Two critical memory-safety flaws in NGINX, tracked as CVE-2026-123633 and CVE-2026-123007, can let unauthenticated attackers run code on servers that have HTTP/2 enabled. Both carry a CVSS 4.0 score of 9.2. F5, which maintains NGINX, released fixes on November 18, 2026.
How CVE-2026-123633 and CVE-2026-123007 Were Found
Wiz Research, Ikotas Labs, Metnir, and Xint each discovered the bugs independently. Wiz says it found both with its Wiz Atlas harness and confirmed their impact using Gemini 4 Carbon and ChatGPT 5.6 Sol. Wiz reported the use-after-free on October 21.
Its report included a proposed fix and an exploit that bypassed ASLR. F5 replied that another team had already reported the same flaw. F5 shared a patch for review on November 10. Wiz reported the second flaw on November 16, and F5 confirmed the next day that it would be fixed in the November 18 release.
Wiz put the findings alongside its PHP2Shell disclosures from last month and Java4Shell, which Calif published a day earlier. Wiz argues that the complexity that once hid memory bugs like these no longer protects them, because AI can now find them. In its view, that also shortens the time between a bug’s disclosure and its exploitation.
Why NGINX Exposure Matters
NGINX powers more than 225 million websites. It often sits in front of several applications as a reverse proxy or load balancer. Because the flaws are in NGINX itself, secure application code offers no protection. A single compromised server could expose multiple sites and APIs to data theft, tampering, or outages.
Inside the Two Bugs
CVE-2026-123633 is nearly six years old and affects versions 1.19.7 through 1.31.8. It occurs when an HTTP/2 connection stays on NGINX’s list of reusable connections after a request has started on it. If connection slots run low while NGINX is proxying to an upstream server, ngx_drain_connections() may close that connection. If building the GOAWAY frame then fails, NGINX frees memory the request is still using. Proxy configurations face the greatest risk.
CVE-2026-123007 dates back to version 1.9.5 in 2015 and affects releases through 1.31.8. When a stream is canceled, NGINX refunds the unsent data allowance to h2c->send_window without checking the protocol’s maximum. This causes an unsigned underflow in the bounds check for WINDOW_UPDATE frames.
The inflated value later turns into a negative length, which leads to an out-of-bounds memory copy in the TLS send path. Researchers achieved code execution with an ASLR bypass on official 1.31.7 and 1.31.8 builds. The test servers were 64-bit systems serving ordinary static files over HTTPS, with no backend application or third-party modules.
Wiz is withholding its proof-of-concept exploits. It notes that attacks require leaking memory addresses and shaping the heap. Packaged products, where many customers run identical builds, are easier targets. CDNs or WAFs that terminate HTTP/2 may block parts of an attack, depending on how they are implemented.
Patching and Mitigating NGINX
For NGINX OSS, the fixes are in 1.30.7 stable and 1.31.9 mainline. NGINX Plus is affected from R33 and 37.0.0. Versions 37.0.7.1 and 37.2.0.1 fix CVE-2026-123633, and versions 37.0.8.1 and 37.3.0.1 fix CVE-2026-123007.
Teams that cannot upgrade right away should temporarily disable HTTP/2:
- Set http2 off; in affected server blocks on version 1.25.1 or later.
- Remove the http2 parameter from listen directives.
- Test application compatibility, reload NGINX, and confirm the old workers have exited.
- Re-enable HTTP/2 after patching.
Several signs warrant investigation: unexpected worker crashes, commands launched by NGINX, floods of WINDOW_UPDATE frames, and long-lived HTTP/2 connections carrying large amounts of data.
The release also fixes eight other NGINX flaws:
- Three use-after-frees rated 9.2: CVE-2026-121810 (HTTP/3 proxy), CVE-2026-123634 (DNS resolver), and CVE-2026-113425 (mail proxy with auth_http).
- One rated 8.7: CVE-2026-118899, a denial-of-service on servers that support TLS 1.3.
- Three rated 6.9: CVE-2026-120993 (proxy_protocol v2), CVE-2026-125283 (alias with try_files), and CVE-2026-123640 (ssl_preread).
- One rated 6.3: CVE-2026-120967, a client certificate bypass.





































