Published November 18, 2026. We will update this post as new information becomes available. 

What happened 

Today, F5 released security updates for two critical vulnerabilities in NGINX, the open-source web server and reverse proxy that sits in front of an estimated 225 million websites. Researchers from Wiz Research, Ikotas Labs, Metnir, Rapid7, and Xint independently found the flaws and reported them to F5 as part of a coordinated disclosure. 

Both issues are memory-safety bugs in how NGINX handles HTTP/2 traffic. Each is rated Critical (CVSS 4.0 score of 9.2) and can allow an unauthenticated attacker to execute code on the server: 

  • CVE-2026-123633 is a use-after-free in HTTP/2 connection handling. It affects reverse-proxy processing when available connection slots run low, and affects NGINX OSS from 1.19.7. 
  • CVE-2026-123007 is an integer underflow in HTTP/2 flow-control accounting (send_window). Researchers demonstrated code execution against NGINX serving ordinary static files, with no backend application or third-party module involved. It affects NGINX versions going back to 1.9.5, released in 2015. 

Successful exploitation could let an attacker run commands, steal sensitive data, tamper with websites, or disrupt services. Because one NGINX deployment often fronts several applications, the impact can reach multiple sites and APIs. The flaws are in NGINX itself, so applications with secure code can still be exposed. Both require HTTP/2 to be enabled on the affected NGINX server. 

Are you affected? 

You are potentially exposed if you run NGINX OSS or NGINX Plus anywhere in your environment with HTTP/2 enabled and reachable by untrusted clients. This includes NGINX acting as a reverse proxy, load balancer, ingress controller, or origin web server. 

What have we learned so far? 

According to our initial analysis, Cloud WAF and WAF gateway protect out of the box against
both vulnerabilities.  

We continue to monitor the situation, including the publication of further technical details and any reports of exploitation, and will update this post and our protections as needed.  

As an extra safety protection, you can choose to mitigate such attacks with Cloud WAF by choosing the HTTP/2 “client to Imperva” only option for your site. With this option, HTTP/2 is used only between the client and Imperva. Traffic from Imperva to your origin does not use HTTP/2, so attackers cannot reach the vulnerable HTTP/2 code path on your NGINX servers through Imperva. Your visitors keep the performance benefits of HTTP/2 at the edge, and your origin is protected from this attack vector while you patch. 

Patch your NGINX servers 

The mitigation above buys you time; it is not a replacement for patching. Upgrade to a fixed release as soon as you can: 

Product  Fixed releases 
NGINX OSS  1.30.7 (stable), 1.31.9 (mainline) 
NGINX Plus (CVE-2026-123633)  37.0.7.1, 37.2.0.1 
NGINX Plus (CVE-2026-123007)  37.0.8.1, 37.3.0.1 

If you have questions, please contact our support team. 

The post Critical NGINX HTTP/2 Vulnerabilities (CVE-2026-123633 and CVE-2026-123007): What Imperva Customers Need to Know appeared first on Blog.