F5 has disclosed two critical vulnerabilities in NGINX, CVE-2026-123633 and CVE-2026-123007, both in the HTTP/2 module (ngx_http_v2_module). Both are rated 9.2 under CVSS 4.0 (8.1 under CVSS 3.1) and can be triggered remotely without authentication on NGINX servers with HTTP/2 enabled. Successful exploitation can crash NGINX worker processes, corrupt memory and potentially lead to remote code execution on the server.
NGINX is one of the most widely deployed web servers and reverse proxies, often sitting in front of multiple websites and APIs. Because the flaws are in NGINX itself, applications behind an affected NGINX instance can be exposed even when their own code is secure. One of the flaws, CVE-2026-123007, dates back to NGINX 1.9.5, released in 2015. The vulnerabilities were discovered independently by several research teams and reported to F5, which released fixed versions on November 18, 2026.
NGINX HTTP/2 vulnerabilities: key facts
| Fact | Detail |
| CVEs | CVE-2026-123633 (use-after-free, CWE-416); CVE-2026-123007 (integer underflow leading to heap buffer overflow, CWE-191 / CWE-787) |
| Severity | CVSS 4.0: 9.2 (Critical); CVSS 3.1: 8.1 (High) for both |
| Component | NGINX HTTP/2 module (ngx_http_v2_module) |
| Attack | Remote, unauthenticated, no user interaction |
| Required configuration | HTTP/2 enabled. CVE-2026-123633 additionally requires NGINX to proxy requests to a backend and the worker process to be running low on worker_connections |
| Affected NGINX Open Source | CVE-2026-123633: 1.19.7 and later; CVE-2026-123007: 1.9.5 and later (up to the fixed releases below) |
| Fixed NGINX Open Source | 1.30.7 (stable) and 1.31.9 (mainline) |
| Affected / fixed NGINX Plus | R33 and later; fixed in 37.0.8.1 and 37.3.0.1 (see version table below) |
| Workaround | Disable HTTP/2 until patched |
| Exploitation | No known in-the-wild exploitation; public proof-of-concept code for CVE-2026-123007 is available |
What are CVE-2026-123633 and CVE-2026-123007?
Both vulnerabilities are memory-safety flaws in how NGINX processes HTTP/2 traffic.
- CVE-2026-123633 (HTTP/2 connection use-after-free). NGINX keeps a list of idle connections that it may close when it runs out of free connection slots. An HTTP/2 connection could remain on this “reusable” list even after a new request stream started on it. When NGINX is proxying the request to a backend and is running low on worker_connections, it can close and free that connection while the request is still using it, resulting in a use-after-free in the worker process. The fix resets the connection’s reusable status when a new stream is created.
- CVE-2026-123007 (HTTP/2 flow-control integer underflow). When an HTTP/2 stream is terminated, its unsent data is credited back to the connection’s flow-control window. A client could cause this window to exceed its allowed maximum, which breaks NGINX’s buffer size accounting and leads to an out-of-bounds memory write (heap buffer overflow), typically followed by a worker crash. Unlike CVE-2026-123633, this flaw does not require a backend: according to the researchers, it can also affect NGINX instances that only serve static content over HTTP/2. The fix accounts for queued frames when validating the client’s WINDOW_UPDATE.
According to F5, both flaws can lead to denial of service and memory corruption, and code execution is possible on systems where Address Space Layout Randomization (ASLR) is disabled or can be bypassed. Researchers who reported the issues state that they were able to achieve code execution, including bypassing ASLR, on standard 64-bit systems. Both issues affect the data plane only; F5 reports no control-plane exposure.
Which NGINX versions are affected?
Any NGINX deployment with HTTP/2 enabled that runs an affected version should be considered vulnerable. Versions on branches that have reached End of Technical Support are not evaluated by F5; they should be upgraded to a supported fixed release.
| Product | CVE | Affected versions | Fixed versions |
| NGINX Open Source | CVE-2026-123633 | 1.19.7 and later, including 1.30.0 to 1.30.6 and 1.31.0 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| NGINX Open Source | CVE-2026-123007 | 1.9.5 and later, including 1.30.0 to 1.30.6 and 1.31.0 to 1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| NGINX Plus | CVE-2026-123633 | R33 and later; 37.0.0 before 37.0.7.1; 37.1.0 before 37.2.0.1 | 37.0.7.1, 37.2.0.1 |
| NGINX Plus | CVE-2026-123007 | R33 and later; 37.0.0 before 37.0.8.1; 37.1.0 before 37.3.0.1 | 37.0.8.1, 37.3.0.1 |
To address both vulnerabilities, NGINX Open Source users should move to 1.30.7 or 1.31.9, and NGINX Plus users to 37.0.8.1 or 37.3.0.1. Products and container images that bundle NGINX may also be affected; check the relevant vendor’s advisory for their fixed builds.
Additional NGINX vulnerabilities fixed in the same release
The same F5 security release also fixes three other critical NGINX vulnerabilities, each rated 9.2 under CVSS 4.0 and 8.1 under CVSS 3.1. They do not involve HTTP/2, so disabling HTTP/2 does not mitigate them. Upgrading to NGINX Open Source 1.30.7 or 1.31.9, or to NGINX Plus 37.0.8.1 or 37.3.0.1, fixes all five vulnerabilities.
- CVE-2026-123634: a use-after-free when NGINX is configured as a proxy, the proxied server name includes variables, and a Server Side Includes (SSI) or mirror subrequest is sent to a location that resolves the same server name. Affects NGINX Open Source 0.6.18 and later.
- CVE-2026-121810: a use-after-free in configurations that use HTTP/3. Affects NGINX Open Source 1.25.0 and later.
- CVE-2026-113425: a use-after-free when NGINX is configured as a mail proxy. Affects NGINX Open Source 0.5.33 and later.
Is there a patch for the NGINX HTTP/2 vulnerabilities?
Yes. F5 released fixes on November 18, 2026: NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline), and NGINX Plus 37.0.8.1 and 37.3.0.1 (37.0.7.1 and 37.2.0.1 address CVE-2026-123633 only). Linux distributions and other vendors that package NGINX release updates on their own schedules, so organizations using distribution packages or bundled NGINX should track their vendor’s advisory.
How to mitigate the NGINX HTTP/2 vulnerabilities before patching
If upgrading is not immediately possible, disable HTTP/2 on affected NGINX instances, which blocks both vulnerabilities:
- On NGINX 1.25.1 and later, set http2 off; in the affected server blocks.
- On all versions, remove the http2 parameter from listen directives.
- Reload NGINX, confirm that old worker processes have exited, and test application compatibility. Re-enable HTTP/2 after upgrading.
Additional recommended steps:
- Inventory all NGINX deployments, including reverse proxies, load balancers, ingress layers and container images, and identify which have HTTP/2 enabled.
- Prioritize internet-facing instances, and those that proxy traffic to backends.
- Monitor for unexpected NGINX worker crashes or processes launched by NGINX, which can be general signs of exploitation attempts.
Are the NGINX HTTP/2 vulnerabilities being exploited in the wild?
At the time of writing, there are no reports of in-the-wild exploitation. However, public proof-of-concept code for CVE-2026-123007 has been released, including a script that triggers the flaw and an exploit demonstrating unauthenticated remote code execution against a vulnerable NGINX server in a lab environment. Together with the detailed technical write-ups published alongside the disclosure, this significantly shortens the time to working exploits. Given how widely NGINX is exposed to the internet, organizations should treat these vulnerabilities as urgent.
How can Orca help?
Orca enables customers to quickly identify assets running vulnerable NGINX versions, including NGINX installed from OS packages and NGINX bundled in container images, and to understand their exposure in context, including internet accessibility, runtime reachability and asset criticality, so they can prioritize remediation based on real risk rather than CVSS alone. Orca’s runtime sensor can also help detect post-exploitation activity on affected hosts.
