NGINX HTTP/2 Unauthenticated Remote Code Execution (CVE-2026-123633, CVE-2026-123007)

Two critical flaws in the NGINX HTTP/2 implementation could let an unauthenticated attacker execute code with the privileges of the NGINX worker process. F5 has released fixes for most affected versions, and disabling HTTP/2 blocks both until you can patch.

Vulnerability

F5 disclosed two critical memory-safety vulnerabilities in the HTTP/2 implementation of NGINX Open Source and NGINX Plus on November 18, 2026. Both can allow an unauthenticated remote attacker to execute code with the privileges of the NGINX worker process. Both require HTTP/2 to be enabled on a listener.

CVE-2026-123633 is a use-after-free flaw in HTTP/2 connection handling. It occurs when an HTTP/2 connection with no active requests is placed on the NGINX reusable connection list.

When a new request begins on that connection, it isn’t removed from the list. NGINX may be short of connection slots while forwarding the request upstream. If so, it can close the connection and free memory that the in-flight request still uses.

This flaw is reachable in reverse-proxy configurations (proxy_pass) with HTTP/2 enabled on the client-facing listener and limited worker_connections headroom. The attack requires NGINX to be able to open a TCP connection to the attacker.

CVE-2026-123007 is an integer underflow in HTTP/2 flow control. When a client cancels a stream, NGINX miscalculates the remaining send allowance, which can lead to memory being read and written out of bounds. It can be reached on a server that simply serves static files over HTTPS, with no backend or third-party modules involved.

CVE and severity

The vulnerabilities are tracked as CVE-2026-123633 and CVE-2026-123007.

F5 gives both CVEs a CVSS v4.0 base score of 9.2 (critical). For CVE-2026-123633, a CVSS v3.1 base score of 8.1 (high) has also been published.

Impact

Successful exploitation gives code execution as the NGINX worker user. Depending on configuration, this can expose loaded TLS private keys and proxied traffic, and can provide a foothold on the host.

The traffic that triggers CVE-2026-123007 isn’t recorded as normal requests, so it may not appear in access logs.

Researchers have disclosed five NGINX vulnerabilities in total, including others outside the scope of this advisory.

Exploit status

Several research teams have demonstrated working exploits in lab conditions. For CVE-2026-123633, remote code execution has been validated against the official 1.31.8 image with a TLS and HTTP/2 server using proxy_pass. Code execution with an ASLR bypass has been shown on official 1.31.7 and 1.31.8 builds.

A proof of concept for CVE-2026-123007 has been published. The public exploit needs roughly 128 GB of HTTP/2 traffic over a single long-lived connection. It also depends on a specific x86-64 environment, so it’s impractical in many settings. Other approaches may exist, so the risk is reduced but not removed.

As of November 18, 2026, no exploitation in the wild had been reported, and neither CVE was listed in the CISA Known Exploited Vulnerabilities catalog. Public proof-of-concept code typically shortens the time to opportunistic exploitation.

Affected component and versions

The flaws affect the HTTP/2 implementation in NGINX Open Source and NGINX Plus:

  • NGINX Open Source stable branch: CVE-2026-123633 affects 1.30.0 to 1.30.6, and CVE-2026-123007 affects 1.9.5 to 1.30.6. Fixed in 1.30.7.
  • NGINX Open Source mainline: both CVEs affect 1.31.0 to 1.31.8. Fixed in 1.31.9.
  • NGINX Plus 37.0 branch: CVE-2026-123633 affects 37.0.0 to before 37.0.7.1, and CVE-2026-123007 affects 37.0.0 to 37.0.7.1. Fixed in 37.0.8.1.
  • NGINX Plus 37.1 and 37.2: CVE-2026-123633 affects 37.1.0 to before 37.2.0.1, and CVE-2026-123007 affects 37.1.0 to 37.2.0.1. Fixed in 37.3.0.1.
  • NGINX Plus R33 to R36: CVE-2026-123633 affects releases from R33, and CVE-2026-123007 affects R34 to R36. No fixed release had been published at the time of writing.

CVE-2026-123633 was introduced in NGINX 1.19.7, so releases from 1.19.7 onward should be treated as potentially affected. NGINX Plus customers need the later build on their branch to cover both CVEs, which is 37.0.8.1 or 37.3.0.1.

Distribution packages may carry backported fixes without changing the output of nginx -v, so compare the full package version with your distributor’s advisory. Confirm exact ranges against F5 advisories K000163926 (CVE-2026-123007) and K000163928 (CVE-2026-123633).

Fix and mitigation

Patch internet-facing NGINX instances with HTTP/2 enabled first.

  • Inventory all NGINX Open Source and NGINX Plus instances, including containers, appliances and vendor products that embed NGINX. Identify those with http2 on a listen directive or http2 on; set.
  • Upgrade NGINX Open Source to 1.30.7 (stable) or 1.31.9 (mainline), and NGINX Plus to 37.0.8.1 or 37.3.0.1 to cover both CVEs.
  • For NGINX Plus R33 to R36, no fixed release has been published. Follow F5 advisories K000163926 and K000163928 for the upgrade path, and apply the HTTP/2 mitigation below in the interim.
  • Restart or reload NGINX as required. Confirm the running version with nginx -v, or the package version for distribution builds, and confirm that old worker processes have exited.
  • Prioritize internet-facing systems, then reverse proxies and load balancers handling sensitive traffic.

Where patching can’t be done promptly, disabling HTTP/2 on affected listeners blocks both vulnerabilities until patching is complete:

  • For NGINX 1.25.1 and later, set http2 off; in the relevant server blocks.
  • For NGINX 1.9.5 to 1.25.0, remove the http2 parameter from listen directives.
  • Reload NGINX and confirm that old workers have exited.

This change can break clients that require HTTP/2, such as native gRPC, so test application compatibility first. It also doesn’t address the other NGINX vulnerabilities disclosed alongside these two. No other vendor workaround has been published. Re-enable HTTP/2 only after upgrading, and re-evaluate temporary controls once patching is confirmed.

References