NGINX released fixes for two critical HTTP/2 flaws, CVE-2026-123007 and CVE-2026-123633. Both can lead to remote code execution, meaning an attacker runs their own code on the server. Wordfence explains the details for WordPress site owners.

This is the second HTTP/2 server flaw in a week. Apache had a similar one on November 12.

Who is affected

NGINX is the web server software that delivers many WordPress sites. It handles HTTP/2 traffic before requests reach PHP or WordPress.

Wordfence lists these affected versions:

  • CVE-2026-123007: NGINX 1.9.5 to 1.30.6, and 1.31.0 to 1.31.8. F5 rates it Critical, 9.2 on the CVSS v4.0 scale.
  • CVE-2026-123633: affects versions from 1.19.7. It also needs NGINX to forward requests to a backend while a worker is low on connections.

Both need the server to accept HTTP/2. HTTP/2 is off unless the configuration turns it on. NGINX’s source build leaves it out by default, but its prebuilt packages include it, and hosts configure things differently.

What to do

The fixed versions are 1.30.7 (stable) and 1.31.9 (mainline), released November 18.

Updating WordPress, plugins, themes, or Wordfence will not patch NGINX. The Wordfence firewall runs inside PHP, so it can’t stop these flaws, and a scan can’t confirm your patch status.

Your host or server administrator must install the fix. If you use managed hosting, watch for guidance from your provider. If you run your own server, update NGINX and restart it.


End of article