Two critical NGINX HTTP/2 vulnerabilities can let an unauthenticated attacker run code on a server, according to Wiz Research. Both are rated Critical with a CVSS 4.0 score of 9.2, and F5, the company behind NGINX, released fixes in a security update on November 18, 2026.
The flaws are tracked as CVE-2026-123633 and CVE-2026-123007. Both require HTTP/2 to be turned on. Wiz says other researchers found them independently, including Ikotas Labs, Metnir, Rapid7 and Xint.
What the two flaws do
Both are memory-safety bugs in how NGINX handles HTTP/2 traffic.
- CVE-2026-123633 is a use-after-free. A connection’s memory gets freed while a request still needs it. It affects reverse-proxy processing when available connection slots run low.
- CVE-2026-123007 comes from incorrect flow-control accounting that leads to an invalid memory copy. It can also hit NGINX serving content directly.
The bug is in NGINX itself, so a website or API can be exposed even if its own code is secure. Wiz showed code execution on an NGINX server serving plain static files over HTTPS on 64-bit systems, without a backend application or third-party modules. Standard protections such as ASLR don’t stop either bug, because attackers can use them to read memory before running code.
How old the bugs are
The integer underflow behind CVE-2026-123007 goes back to NGINX 1.9.5 in 2015, so it sat in the code for more than a decade. The use-after-free had been there for nearly six years.
Wiz found both using Wiz Atlas, the system behind its AI code scanning, then used Gemini 4 Carbon and ChatGPT 5.6 Sol to confirm that an unauthenticated attacker could execute code. It links the finds to the PHP2Shell flaws it reported last month and Java4Shell, disclosed a day earlier by Calif. Its view: AI is lowering the barrier to finding memory bugs that once took painstaking tracing, for attackers as well as defenders.
Disclosure timeline
- October 21: Wiz reports the use-after-free to F5. F5 says another team had already reported it.
- November 10: F5 sends a patch for review.
- November 16: Wiz reports the second flaw.
- November 17: F5 confirms it matches CVE-2026-123007 and is in the planned release.
- November 18: F5 publishes the update and coordinated disclosure.
The F5 update also fixes several other NGINX vulnerabilities.
What administrators should do now
Wiz advises finding NGINX deployments with HTTP/2 enabled and upgrading to a release that fixes both bugs. Start with servers an attacker can reach from the internet. One NGINX instance often serves several applications, so a single compromise can reach many sites and APIs.
If you can’t upgrade right away, temporarily disable HTTP/2, test application compatibility, reload NGINX and confirm the old workers have exited. Turn HTTP/2 back on after upgrading.
For detection, Wiz suggests investigating unexpected NGINX worker crashes or commands launched by NGINX. It stresses these are general warning signs, not confirmed indicators of these bugs.
How the use-after-free happens
Wiz explains that NGINX keeps a list of idle connections it can close when it needs room for new ones. An HTTP/2 connection joins that list when it has no active requests and should leave it once a request starts. In CVE-2026-123633 it doesn’t. An attacker sends only part of a request’s headers, then the rest, so NGINX treats the connection as safe to close while a request is still running.
When free connection slots run low, for example while opening a connection to an upstream application server, NGINX can pick that connection to close. If an internal frame limit blocks the goodbye message to the client, the error path frees the connection’s memory while the request still uses it. The freed memory can be reused for other data, which is the basis for code execution.
The flow-control bug
HTTP/2 lets several requests share one connection, with a counter limiting how much response data NGINX may send. If a stream is canceled while data is queued, the unused allowance is returned to that counter. Wiz says the refund doesn’t check HTTP/2’s maximum, which leads to the invalid memory copy in CVE-2026-123007.
Why patch speed is the issue
Wiz warns that faster discovery means a shorter window between disclosure and exploitation, while turning a published fix into production protection still takes manual work such as validating patches and coordinating rollouts. Its advice is to focus on how quickly you can cut exposure.
Administrators should treat the NGINX HTTP/2 vulnerabilities as urgent for any internet-facing proxy, then confirm the fixed version is deployed. The details come from Wiz Research’s write-up.
Source: wiz.io