Wiz researchers got a vulnerable NGINX server to run code over an ordinary HTTPS connection while it was serving static files. The test of CVE-2026-123007 showed that a site can be exposed through its web server even when it has no backend application. F5 disclosed that flaw and a second NGINX HTTP/2 vulnerability, CVE-2026-123633, on November 18. If your NGINX instance accepts HTTP/2 connections, check its running build and move to a release that fixes both. [1] [2] [3]
Why serving static files still exposes NGINX
HTTP/2 flow control helps each side of a connection manage how much data it can send. With CVE-2026-123007, an error in that accounting can cause NGINX to copy data outside an allocated buffer. The worker can crash, and F5 says remote code execution is possible in certain conditions. Wiz confirmed code execution in a lab on official 64-bit NGINX 1.31.7 and 1.31.8 builds over TLS. Serving a file directly still uses this part of the server. [1] [2]
CVE-2026-123633 applies when NGINX accepts HTTP/2 from clients and proxies their requests to a backend. When the worker runs low on available connections, NGINX can free a connection’s memory while a request still needs it. Using that memory can crash the worker or allow code to run with its privileges. Both flaws can be reached without signing in to the application. F5 scores each 9.2 Critical under CVSS 4.0 and 8.1 High under CVSS 3.1. [1] [2] [3]
Wiz found both flaws with AI-assisted source code analysis and then tested their impact in the lab. Other research teams independently reported the flaws to F5. The static-file issue had been in the NGINX code since 2015. [1]
Which NGINX versions fix both HTTP/2 bugs?
- NGINX Open Source. Install 1.30.7 stable, 1.31.9 mainline, or a later release in your branch.
- NGINX Plus. Install 37.0.8.1, 37.3.0.1, or a later release with both fixes.
- Distribution packages and bundled NGINX. Check the maintainer’s fixed package or image. Canonical lists fixed Ubuntu packages in USN-9159-1. [4]
In upstream Open Source builds, CVE-2026-123007 dates back to 1.9.5 and CVE-2026-123633 to 1.19.7. NGINX Plus 37.0.7.1 and 37.2.0.1 already cover CVE-2026-123633. If you installed either of those builds, CVE-2026-123007 still requires a newer update. [2] [3]
Check the NGINX that actually accepts HTTP/2
Start with the active configuration on the web server or reverse proxy. If you use a CDN or load balancer, check the connection from that service to your NGINX origin as well as the public endpoint. A browser’s HTTP/2 connection to the CDN tells you which protocol the CDN accepts. Check the origin separately, including any listener reachable directly. An inventory of active features also helps with other configuration-specific issues, such as the earlier NGINX regex map vulnerability.
For a host install, check the build with nginx -v and match the full package version to the vendor’s advisory if you use a distribution package. Test the configuration with nginx -t and restart the service so it runs the updated executable. For containers, rebuild or pull the fixed image, redeploy it, and check the image digest of the running workloads. For managed hosting, ask the provider which running build contains both fixes.
If you need time to stage the upgrade, temporarily disable HTTP/2 on the affected listeners. NGINX 1.25.1 and later supports http2 off;. Remove any legacy http2 parameters from the affected listen directives, test client compatibility and the configuration, then reload and confirm old workers have exited. This reduces exposure to these two HTTP/2 flaws while you install the update. [5] [6]
References
- Wiz Research. Unauthenticated remote code execution in NGINX. November 18, 2026.
- F5. NGINX HTTP/2 advisory for CVE-2026-123007. November 18, 2026.
- F5. NGINX HTTP/2 advisory for CVE-2026-123633. November 18, 2026.
- Canonical. Ubuntu security notice USN-9159-1. November 19, 2026.
- NGINX. HTTP/2 directive documentation. Accessed November 20, 2026.
- CERT-EU. Critical vulnerabilities in Nginx. November 18, 2026.

