Cloudflare Shields nginx Origins From Three of Five New Flaws

Cloudflare says its HTTP proxy blocks attacks against three newly disclosed nginx flaws, provided attackers cannot connect directly to the origin server. Administrators still need to install fixed…

Nov 20, 2026
•
3 min read
Technobezz
Cloudflare Shields nginx Origins From Three of Five New Flaws

Don't Miss the Good Stuff

Get tech news that matters delivered to your inbox.

Cloudflare says its HTTP proxy shields nginx servers from three newly disclosed vulnerabilities affecting HTTP/2 and HTTP/3, provided attackers cannot bypass it and reach the servers directly. Administrators should install nginx 1.30.7, nginx 1.31.9 or a corrected vendor build, then restart, the company advises. The protection does not fully cover a separate resolver flaw and does not cover the mail proxy vulnerability.

F5 and nginx.org disclosed ten nginx vulnerabilities on November 18, including five memory corruption bugs investigated by Xint under the nginx2root name. Those five can let attackers without authentication crash a worker process or, according to Xint, execute server commands. F5 assigns each a CVSS 4.0 score of 9.2, rated Critical, and says executing code requires defeating or disabling Address Space Layout Randomization.

Cloudflare identifies CVE-2026-123007 as the biggest concern because enabling HTTP/2 is enough to expose the affected functionality, which dates to nginx 1.9.5. Censys counted about 8.8 million services using potentially vulnerable versions with HTTP/2 enabled as of November 19. Cloudflare cautions that reported version numbers cannot establish vulnerability because distributions may have incorporated fixes into older builds.

For proxied hostnames, Cloudflare handles the client's HTTP/2 or HTTP/3 connection itself, then establishes a separate connection with the origin. The company says that prevents malicious protocol frames from reaching nginx, even when its own origin connection uses HTTP/2. But an attacker who can connect directly to the origin's IP address can bypass that protection, making restricted origin access a condition of the shield.

The resolver vulnerability depends on a combination of configuration choices involving proxy_pass, variables and subrequests; Cloudflare says its proxy cannot provide complete protection against it. The mail flaw requires an nginx mail proxy using proxy on and auth_http, and Cloudflare's HTTP proxy does not transport mail. Cloudflare says its own edge is unaffected, with an update addressing the relevant paths deployed worldwide before disclosure.

Xint also found a Linux kernel flaw that can turn execution as an nginx worker into root access, demonstrating the escalation from within a Docker container. As of November 18, a kernel fix was unavailable and Xint was holding back details pending a patch. Cloudflare said it had seen no reports of attacks exploiting the five nginx flaws in the wild as of November 19, although Rapid7 had published a limited proof of concept.

Share