PSA: Critical NGINX HTTP/2 Vulnerabilities: What WordPress Site Owners Should Know
NGINX has released fixes for two critical HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633. Both can lead to remote code execution on affected servers. If your WordPress site uses NGINX, keep an eye out for guidance from your hosting provider about whether its servers are affected and patched. NGINX lists versions 1.9.5–1.30.6 and 1.31.0–1.31.8 as affected by ...Read More
NGINX has released fixes for two critical HTTP/2 vulnerabilities, CVE-2026-123007 and CVE-2026-123633. Both can lead to remote code execution on affected servers. If your WordPress site uses NGINX, keep an eye out for guidance from your hosting provider about whether its servers are affected and patched.
NGINX lists versions 1.9.5–1.30.6 and 1.31.0–1.31.8 as affected by CVE-2026-123007; CVE-2026-123633 starts at 1.19.7. Fixed open-source versions 1.30.7 (stable) and 1.31.9 (mainline) were released November 18, 2026. Both flaws require NGINX to accept client HTTP/2. CVE-2026-123633 also requires forwarding requests to a backend while a worker runs low on connections. HTTP/2 is off unless a server’s configuration enables it. NGINX’s source build omits the HTTP/2 module by default, but NGINX’s own prebuilt packages include it, and hosting configurations vary.
Why This Is Important for WordPress Sites
NGINX can serve a WordPress site or sit in front of its application server. It handles HTTP/2 before requests reach PHP or WordPress. Successful exploitation could run code with the NGINX worker’s privileges, putting sites and data on that server at risk.
Updating WordPress, plugins, themes, or Wordfence will not patch NGINX. The Wordfence firewall runs at the PHP application layer. Your host or server administrator must install the server fix; a Wordfence scan cannot confirm its patch status.
What We Know
F5 rates CVE-2026-123007 Critical at 9.2 under CVSS v4.0, and its second advisory gives CVE-2026-123633 the same rating. Wiz reports lab code execution for both flaws; Metnir reports it for CVE-2026-123633.
Rapid7 published an RCE proof of concept for CVE-2026-123007, tailored to a freshly started local Docker target. Its demonstrated method needs substantial traffic, but that does not rule out other methods. Xint, which F5 credits for CVE-2026-123007, reports code execution over public HTTPS on AWS, GCP, and Azure under concurrent normal traffic. It also reports chaining the NGINX flaw with a separate Linux kernel bug to gain root in its tests. CERT-EU reported no known exploitation in the wild on November 18.