Critical NGINX HTTP/2 Vulnerabilities Allow Remote Code Execution
NGINX has released fixes for two critical HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633, which could lead to remote code execution on affected servers.

NGINX has issued patches for two critical vulnerabilities in its HTTP/2 implementation, identified as CVE-2026-123007 and CVE-2026-123633. Both flaws carry the potential for remote code execution (RCE) on vulnerable systems, posing a significant risk to servers, particularly those hosting WordPress sites. The vulnerabilities affect NGINX versions 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 for CVE-2026-123007, while CVE-2026-123633 impacts versions starting from 1.19.7. Fixed versions, 1.30.7 for the stable branch and 1.31.9 for the mainline branch, were released on November 18, 2026.
Exploitation of these vulnerabilities requires that the NGINX server is configured to accept HTTP/2 connections. While NGINX's source build does not include the HTTP/2 module by default, pre-built packages often do, and hosting environments can vary in their configurations. CVE-2026-123633 has an additional prerequisite: the server must be forwarding requests to a backend while a worker process is experiencing low connection availability. For WordPress site owners, this means that while updating WordPress itself or its plugins will not mitigate these NGINX-specific flaws, their hosting provider must apply the server-side patches.
Security researchers have assigned critical severity ratings to both vulnerabilities. F5 rated CVE-2026-123007 at 9.2 under CVSS v4.0, with CVE-2026-123633 receiving the same critical rating. Proof-of-concept (PoC) exploits have been demonstrated in lab environments, with some researchers showing code execution capabilities. Notably, one PoC for CVE-2026-123007 was tailored for a Docker environment, and another report suggests that CVE-2026-123633 could be chained with a Linux kernel vulnerability to achieve root privileges. While initial reports from CERT-EU on November 18 indicated no known exploitation in the wild, the existence of PoCs and the critical ratings necessitate prompt action.
For WordPress site owners using managed or shared hosting, the primary course of action is to monitor security announcements from their hosting providers. These providers are responsible for patching the NGINX instances that serve client websites. If an update is not yet available, users should continue to watch for official communications. For those managing their own NGINX servers, it is crucial to verify the NGINX package version and confirm the active HTTP/2 configuration. This includes checking any reverse proxies or containerized deployments. It's also important to note that fixes might be backported by vendors, potentially retaining older NGINX version numbers.
If immediate patching is not feasible for self-managed NGINX instances, a temporary mitigation is to disable HTTP/2 on affected listeners. This can be achieved by removing the http2 directive from relevant listen statements and, for NGINX versions 1.25.1 and later, by setting http2 off;. After applying this change, the NGINX configuration should be reloaded and tested to ensure HTTP/2 is no longer accepted. It is important to remember that this mitigation only addresses these specific HTTP/2 vulnerabilities and does not cover other potential security issues fixed in the same NGINX release.
The discovery timeline indicates that CVE-2026-123633 was found by Metnir around August 29, 2026, and reported to F5 on September 12. CVE-2026-123007 was discovered by Xint around October 11 and reported to F5 on October 16. The coordinated release of patches on November 18 signifies a swift response from NGINX and F5 to address these critical security flaws.
In conclusion, the critical NGINX HTTP/2 vulnerabilities present a serious threat that requires attention from both hosting providers and server administrators. While the immediate impact on WordPress sites is dependent on the server configuration and the adoption of HTTP/2, the potential for RCE makes these flaws a priority. Users should update their NGINX installations to the patched versions or implement temporary mitigations if updates are delayed, ensuring the security of their web infrastructure.
This new report from The Register details 10 vulnerabilities in open source NGINX, including critical RCE flaws (CVE-2026-123633, CVE-2026-123007) affecting HTTP/2. These memory-safety issues, discovered with AI assistance, allow unauthenticated attackers to hijack servers powering millions of websites, with one vulnerability existing for at least 10 years. A proof-of-concept demonstrating RCE against a Docker image has also been released.
This new report details the specific technical mechanism of CVE-2026-123007, an integer underflow in NGINX's HTTP/2 protocol handling that can lead to remote code execution. Researchers demonstrated chaining this flaw with a Linux kernel vulnerability to achieve full server control, though the exploit has practical limitations related to traffic volume and network speed. The article also highlights that the vulnerability was discovered by multiple independent teams, including one using an AI-driven testing harness, and notes that nearly all identifiable NGINX hosts were running affected versions.