nginx fixed HTTP/2 memory bugs, and a proof of concept is public. Upgrade to 1.30.7 or 1.31.9

By George Bailey   Published: 11/19/26   4 min read

nginx shipped 1.30.7 and 1.31.9 on November 18 with fixes for ten security bugs. The two that matter most sit in HTTP/2, which most public nginx servers have turned on. F5, which maintains nginx, says each of the five worst can crash a worker and can lead to code execution when ASLR is off or bypassed.

Get the CyberExperts Daily Brief: the day's top security news in 5 minutes. Free.

Rapid7 published a working proof of concept for the main HTTP/2 bug the same day. No attacks have been reported.

If your nginx speaks HTTP/2, the upgrade belongs on this week’s list.

nginx 1.30.7 and 1.31.9 fix five worker memory bugs

CVE-2026-123007 is a flow-control bug in HTTP/2. A client cancels queued response data, nginx refunds the send window without checking its limit, and a later copy uses a bad length. nginx rates it major; it affects 1.9.5 through 1.31.8.

CVE-2026-123633 is a use-after-free in HTTP/2 when a worker runs low on connections (1.19.7 and later). The others in F5’s top five need specific setups: HTTP/3 (CVE-2026-121810), the resolver with SSI or mirror subrequests (CVE-2026-123634) and the mail proxy (CVE-2026-113425).

Any nginx with HTTP/2 turned on is in range

Rapid7’s exploit needs about 128 GB of HTTP/2 traffic and worked against a fresh Docker container, so it is not a one-packet attack. On a link slower than about 300 Mbit/s it runs past nginx’s one-hour connection limit. Wiz says it also reached code execution with an ASLR bypass on official 1.31.7 and 1.31.8 builds, and it is keeping its exploit private.

Distribution packages count too. AlmaLinux says versions 8, 9 and 10 all ship affected nginx and has released patched packages, so a server that installs nginx from the OS repository needs the OS update, not a source build.

Upgrade nginx, or switch HTTP/2 off until you can

Forward this

For whoever runs our websites and load balancers: nginx, the web server in front of many of our sites, fixed memory bugs on November 18 and a proof of concept is public. Can someone confirm every nginx server is on 1.30.7 or 1.31.9 (or the patched OS package) and reloaded?

Details

Hunt / verify

Source: nginx advisories; Rapid7 write-up

Sources

George Bailey

George Bailey is the byline of the CyberExperts editorial desk, the team behind the CyberExperts Daily Brief. The desk covers vulnerabilities, breaches and security news from vendor advisories, CISA alerts and other primary sources, and links those sources in every story. Questions or corrections: [email protected].