Skip to content
feed: live
0dayNews
f5

NGINX HTTP/2 Flaw CVE-2026-123007: Patch to 1.30.7

A decade-old NGINX HTTP/2 flaw can lead to code execution without login. Fixed in 1.31.9 and 1.30.7. No exploitation reported yet, but a public PoC exists.

NGINX HTTP/2 Flaw CVE-2026-123007: Patch to 1.30.7
Image: AI-generated — conceptual illustration, not incident evidence / 0dayNews AI Cover · Generated on-site infrastructure — no external license
fuseMarisol "Fuse" Delgado·Published ·2 min read

NGINX fixed CVE-2026-123007 on November 18, a flaw in its HTTP/2 support that can let an unauthenticated attacker run code on the server. Patch this first on any NGINX box that speaks HTTP/2 to the internet. Nobody has reported attacks yet, which is exactly the window you want.

What changed

Per The Hacker News, the bug has been in NGINX open source since version 1.9.5, released September 22, 2015. Every open-source release from 1.9.5 through 1.31.8 is affected. NGINX Plus is affected in 37.x releases before the fixed builds and in R34 to R36.

F5 says code execution is possible where ASLR (address space layout randomization) is off or can be bypassed. Researchers at Wiz said they bypassed ASLR in tests. Code runs with the permissions of an NGINX worker process, so reaching root needs a second bug. Xint’s researchers chained one in the Linux kernel, even with NGINX in a Docker container.

Exploitation status

Neither the vendor nor the Wiz and Rapid7 researchers have reported in-the-wild exploitation. It was not in CISA’s Known Exploited Vulnerabilities catalog as of November 18. Public proof-of-concept code exists on GitHub, though its notes say it only suits a demonstration against a freshly started container. We are not describing how it works.

What to do

  • Upgrade to NGINX 1.31.9 (mainline) or 1.30.7 (stable). Both fix all five flaws released in this batch.
  • On NGINX Plus, the fixed builds are 37.3.0.1 and 37.0.8.1. For R34 to R36, no fix was listed.
  • Restart fully or use the live binary upgrade. A reload alone leaves the old executable running and old workers can keep serving existing connections.
  • Official Docker images carry the 1.31.9 and 1.30.7 tags, including Alpine variants.
  • Ubuntu and Debian had not shipped fixed packages as of November 18. A distribution package can carry a fix without changing the version string, so check the distro tracker, not just nginx -v.
  • Behind a CDN, check the NGINX origin itself. An origin that accepts only HTTP/1.1 cannot be reached through HTTP/2.

Priority call

Patch internet-facing HTTP/2 servers first. The same release fixes four more flaws that the vendor says can lead to code execution under the same ASLR condition: CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425. Each needs a particular setup, such as HTTP/3 enabled or NGINX used as a mail proxy. Check which features you run, then deprioritize the ones you do not.

Analysis: a ten-year-old bug with a public PoC and a vendor patch on the same day tends to draw scanning quickly. That is a pattern, not a report of attacks.

For earlier NGINX fixes, see F5 NGINX Out-of-Band Patches. More on the F5 hub.

Found this useful? Share it.