← All articles

Critical NGINX HTTP/2 flaws put WordPress servers at risk

Critical NGINX HTTP/2 flaws put WordPress servers at risk

NGINX HTTP/2 vulnerabilities can allow remote code execution on affected servers, creating a serious risk for WordPress sites that use NGINX. NGINX released fixes for CVE-2026-123007 and CVE-2026-123633 on November 18, 2026. Site owners should look for guidance from their hosting provider because updating WordPress, plugins, themes or Wordfence does not patch the web server itself.

NGINX is web server software that can deliver a WordPress site directly or operate in front of the application server. It handles HTTP/2 requests before they reach PHP, the software that runs WordPress. Remote code execution means an attacker may be able to make the server run commands of their choosing from another computer. If exploitation succeeds, the code runs with the privileges of the NGINX worker, potentially placing websites and data on that server at risk.

NGINX lists versions 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 as affected by CVE-2026-123007. CVE-2026-123633 affects versions starting at 1.19.7. The fixed open-source releases are 1.30.7 for the stable branch and 1.31.9 for the mainline branch. Both flaws require NGINX to accept client HTTP/2 connections. HTTP/2 is a newer version of the web communication protocol, and it is disabled unless the server configuration enables it.

The NGINX source build does not include the HTTP/2 module by default, but NGINX’s prebuilt packages do include it. Hosting configurations vary, so the version number alone may not tell a site owner whether the relevant risk is present. CVE-2026-123633 has an additional condition: NGINX must be forwarding requests to a backend while one of its workers is running low on available connections.

F5 rates CVE-2026-123007 as Critical, with a CVSS v4.0 score of 9.2. CVSS is a standard system for describing the severity of security flaws. F5 gives CVE-2026-123633 the same rating in its second advisory. Wiz reports laboratory code execution for both vulnerabilities, while Metnir reports code execution for CVE-2026-123633.

Rapid7 published a remote code execution proof of concept for CVE-2026-123007. Its demonstration was tailored to a freshly started local Docker target, and the method required substantial traffic. That requirement does not rule out other attack methods. Xint, which F5 credits with CVE-2026-123007, reports code execution over public HTTPS on AWS, GCP and Azure while the systems carried concurrent normal traffic. Xint also reports chaining the NGINX flaw with a separate Linux kernel bug to gain root access in its tests. Root access is the highest level of control on a Linux system. CERT-EU reported on November 18 that it knew of no exploitation in the wild.

WordPress Site Health cannot confirm whether a hosting provider’s NGINX package is patched or whether the server accepts HTTP/2. The Wordfence firewall operates at the PHP application layer, and a Wordfence scan cannot establish the patch status of NGINX. If a site uses managed or shared hosting, its owner should monitor the provider’s security announcements and status updates for advice about CVE-2026-123007 and CVE-2026-123633.

Server administrators should check the installed NGINX package and the active HTTP/2 configuration, including reverse proxies and containers. A reverse proxy is a service that receives web requests before passing them to another server, while a container is an isolated package used to run software. Administrators should follow their vendor’s advisory because a backported fix may be applied without changing the older NGINX version number.

A public HTTP/2 connection may end at a content delivery network, or CDN, rather than at the NGINX origin server. A CDN is a network that receives and delivers website traffic from locations near visitors. Administrators therefore need to check the origin and any direct route to it, not only what the public connection appears to show.

Self-managed NGINX administrators should install version 1.30.7, version 1.31.9 or their vendor’s fixed package, then restart NGINX so the new program is loaded. Containers should be recreated from patched images. NGINX Plus users should check F5’s fixed releases for both CVEs.

If an affected NGINX listener cannot yet be updated, administrators can temporarily disable HTTP/2 by removing `http2` from the relevant `listen` directives. On NGINX 1.25.1 or later, they should also set `http2 off;`. The configuration must then be tested and reloaded, followed by verification that HTTP/2 is no longer accepted. This temporary measure blocks the two described HTTP/2 attack paths, but it does not fix other vulnerabilities addressed in the same NGINX release.

Metnir says it found CVE-2026-123633 on August 29, 2026, and reported it to F5 on September 12. Xint says it discovered CVE-2026-123007 on October 11 and reported its findings to F5 through HackerOne on October 16. NGINX released the fixes on November 18. For site owners who want the server layer handled as part of their hosting arrangement, AEU Hosting offers managed WordPress hosting, secured end to end.

Also available in: DeutschItalianoShqip