AI NewsInfrastructureAnnouncement
Five nginx bugs let an attacker run code on a server
Cloudflare says five memory bugs in nginx, grouped under the name nginx2root, let an attacker run code on a server. Three were disclosed this week in addition to the two HTTP/2 bugs patched on 18 November.

Image: Cloudflare
Why it mattersIf you run nginx anywhere, patch to 1.30.7 or 1.31.9. Behind Cloudflare, the worst bug cannot reach your origin because Cloudflare terminates every HTTP/2 connection at its edge.
An open-source web server used by most of the public internet has five memory bugs disclosed in one week. Cloudflare published a joint advisory on 20 November. The vendor groups them under the name nginx2root. Each one lets an unauthenticated attacker run code on the server.
Two of the five were disclosed on 18 November. Cloudflare says Xint researchers reported them under the nginx2root name. Three more are in the same group. CVE-2026-123007 is an integer overflow in the HTTP/2 flow control code. CVE-2026-123633 is a use-after-free in the HTTP/2 proxy. CVE-2026-121810 is a use-after-free in the HTTP/3 proxy. CVE-2026-123634 is a use-after-free in the resolver. CVE-2026-113425 is a use-after-free in the mail proxy.
Which bug a reader should treat as most serious
Cloudflare says CVE-2026-123007 has the widest reach. It only needs HTTP/2 turned on. That is the common setting on any TLS deployment. Every nginx since 1.9.5, released in September 2015, is affected. Cloudflare says it scanned 11.94 million nginx servers that reported a version. Of those, 98.9 percent fell in the affected range. Censys counted about 8.8 million services running a potentially affected version with HTTP/2 enabled on 19 November.
Xint ran the exploit over the public internet on 10 November, eight days before disclosure. That tells a defender the bug is reachable in the real world.
What Cloudflare says it did
Cloudflare says a block for CVE-2026-123007 rolled out globally before the bugs were published. The protection does not come from the Cloudflare WAF. It comes from how Cloudflare proxies traffic. Cloudflare terminates every client HTTP/2 and HTTP/3 connection at its edge. It opens a separate connection to the origin. The attack frames never reach the origin nginx. Control frames are consumed at the edge and are not forwarded.
That block only works if the origin is not reachable another way. Cloudflare says customers should check that direct access is closed. The three options named are Cloudflare Tunnel, IP allowlisting, and Authenticated Origin Pulls.
What to do if nginx runs where a reader can reach it
Cloudflare and nginx agree on the patch. Update to nginx 1.30.7 or 1.31.9, or a vendor build with the same fixes, and restart. For nginx Plus, the fixed releases are 37.0.8.1 and 37.3.0.1. If a patch cannot land today, turning HTTP/2 off on exposed listeners stops the worst of the five.
The resolver and mail proxy bugs apply to fewer deployments. CVE-2026-123634 needs the resolver to be used for proxy variables, which is a rare configuration. CVE-2026-113425 needs the mail proxy and auth_http. The other two HTTP use-after-frees need upstream proxying, which is the common nginx setup.
For a team building software, the detail to notice is the discovery pattern. Cloudflare credits Xint, Wiz Research, Ikotas Labs, Metnir, Palo Alto Networks Unit 42 and Rapid7 across the five CVEs. Five teams found five memory bugs in one codebase in one window. The cost of finding this kind of bug has come down. A ten-year-old integer overflow sat in HTTP/2 flow control the whole time. The team that runs nginx this week should check which version is on each server. The team that writes software should ask a harder question. Which open-source dependency gets less scrutiny than this one did?
Source
nginx2root: Five new nginx vulnerabilities, and how Cloudflare protects origins from the worst of them, Cloudflare blog.
This item was written by an AI system from the linked source. Reveneau is responsible for what it publishes.
Get AI News in your inbox
New developer tools, model and agent releases, and how teams are actually using them to release software. Short, and only when there is something worth reading.

