(647) 243-4688

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.

How to Check Whether Your Server Is Exposed

WordPress Site Health cannot confirm whether your host’s NGINX package is patched or whether the server accepts HTTP/2. If you use managed or shared hosting, watch your provider’s security announcements and status updates for guidance on these CVEs. If no update is available yet, continue monitoring its official channels.

If you manage the server, check its NGINX package and active HTTP/2 configuration, including reverse proxies and containers. Follow your vendor’s advisory: backported fixes may retain older NGINX version numbers. A site’s public HTTP/2 connection may terminate at a CDN rather than the NGINX origin; check the origin and any direct route to it.

What to Do Now

  • Managed or shared hosting: Watch for your host’s security announcements and follow any guidance it provides about these CVEs.
  • Self-managed NGINX: Install 1.30.7, 1.31.9, or your vendor’s fixed package, then restart NGINX to load the new binary. Recreate containers from patched images. For NGINX Plus, check F5’s fixed releases for CVE-2026-123007 and CVE-2026-123633.
  • If you manage NGINX and cannot update yet: Temporarily disable HTTP/2 on affected NGINX listeners. Remove http2 from relevant listen directives; on NGINX 1.25.1 or later, also set http2 off;. Test and reload the configuration, then verify HTTP/2 is no longer accepted. This does not address other vulnerabilities fixed in the same NGINX release.

Timeline

Conclusion

If your WordPress site uses NGINX, watch for your hosting provider’s guidance on these CVEs. Server administrators should install a fixed NGINX or vendor package and restart NGINX. Disabling HTTP/2 temporarily blocks these two attack paths, but does not address other vulnerabilities fixed in the same release.

The post PSA: Critical NGINX HTTP/2 Vulnerabilities: What WordPress Site Owners Should Know appeared first on Wordfence.