VulnerabilitiesAppliance Security

NGINX2Root: Five Critical NGINX Bugs, a Public PoC, and the Products You Forgot Run NGINX

November 22, 2026 · Brian Deitch

I'm four days late on this one, and I'm writing it anyway because the second wave is the part that matters. F5 shipped an out-of-band NGINX release on November 18 fixing five critical bugs the researchers call NGINX2Root. Since then, the vendors who embed NGINX inside their own products have been publishing "are we affected" advisories one by one. If you only patched the NGINX boxes you know about, you're not done.

What F5 Fixed

Xint (Theori) found all five and reported them to F5 in October. Each is rated CVSS 4.0 9.2 (3.1 8.1):

  • CVE-2026-123007: integer underflow in HTTP/2 flow control, leading to heap out-of-bounds read and write. Affects NGINX 1.9.5 through 1.31.8. Needs only HTTP/2 enabled.
  • CVE-2026-123633: use-after-free in HTTP/2 proxying when worker connections run low.
  • CVE-2026-121810: the same class of bug in HTTP/3 (QUIC).
  • CVE-2026-123634: use-after-free in the DNS resolver when a variable proxy_pass meets mirror or SSI subrequests.
  • CVE-2026-113425: use-after-free in the mail proxy auth_http path.

Fixed in NGINX 1.30.7 (stable) and 1.31.9 (mainline), and NGINX Plus 37.0.8.1 and 37.3.0.1. NGINX Plus R33 through R36 get no patch, so those need to move to 37.x. Older open source branches get no upstream fix either; you're relying on your distro's backport.

How Worried Should You Be?

Honestly: worried enough to patch this week, not enough to panic. No in-the-wild exploitation had been reported as of the latest updates I could find, and none of the five is on CISA's KEV list. But Rapid7's Stephen Fewer published a working proof of concept for CVE-2026-123007 on November 18. Rapid7 itself describes it as constrained: it needs ASLR defeated, a specific glibc build, and roughly 128 GB of HTTP/2 traffic, and it's unlikely to work behind a proxy that terminates HTTP/2. Xint and Wiz say they have exploits they're holding back. Sophos also warns that fake exploit repos are circulating, so don't run random GitHub code against your own servers.

Credit to the researchers for responsible disclosure, and to F5 for shipping five fixes at once with clear preconditions. Clear "you're only affected if" language is a gift to defenders.

The Part People Miss: Embedded NGINX

Standard disclosure: I work at Zscaler, which competes with Palo Alto Networks, so weigh my framing accordingly. Every vendor ships third-party code with bugs in it, mine included.

NGINX is inside a lot of products. Palo Alto Networks published a portfolio advisory covering CVE-2026-123007 and CVE-2026-123633, and I want to credit how clear it is:

  • Affected: PAN-OS and Panorama, but "only" for customers who enable HTTP/2. Affected ranges include 12.2.0 up to 12.2.4-h3, several 12.1 builds from 12.1.5, and several 11.2 builds from 11.2.8.
  • Fixes: 12.2.4-h3, 12.1.10-h6 and 11.2.16-h3 are out; 12.1.7-h15, 11.2.10-h19 and 11.2.13-h6 have an ETA of November 23.
  • Not affected: PAN-OS 12.1.2 through 12.1.4 builds and 11.2.0 through 11.2.7 builds.
  • Exploitation: Palo Alto says it is "not aware of any malicious exploitation."
  • Workaround: disable HTTP/2 on PAN-OS and Panorama.
  • SaaS: Palo Alto says it is managing the backend rollout for its SaaS products with no customer action needed.

Sophos published a similar advisory: its hosted Taegis XDR and VDR services are fixed, a long list of products don't include the component, and it's still investigating Sophos Firewall. Sophos also flags that OpenResty and Kubernetes ingress controllers embed NGINX and need their own updates.

The architecture point isn't "Palo Alto bad." It's that every appliance you own is a bundle of open source components, and a bug in one of them turns into a patch on a box you have to schedule yourself. The more internet-facing appliances you run, the more of these portfolio advisories you have to track. That's the real cost of the model, and it applies to every appliance vendor.

What To Do

  • Find every NGINX, not just the ones your web team owns: reverse proxies, ingress controllers, OpenResty, containers with their own base images, and vendor appliances.
  • Upgrade and restart. A config reload doesn't replace the running binary.
  • If you can't patch today: disabling HTTP/2 covers CVE-2026-123007 and CVE-2026-123633; disabling HTTP/3 covers CVE-2026-121810; use a fixed upstream instead of a variable proxy_pass for CVE-2026-123634; and keep mail proxy listeners off the internet for CVE-2026-113425.
  • PAN-OS and Panorama customers: check whether HTTP/2 is enabled. If it is, apply the listed hotfix (some land November 23) or disable HTTP/2 until you can. Either way, keep the management interface restricted to trusted IPs.
  • Watch your other vendors. Search their advisory pages for CVE-2026-123007 this week. Expect more to publish.

Bottom Line

Five 9.2s, one constrained public PoC, no known exploitation yet. That's a window, not a pass. Patch the NGINX you know about, then go find the NGINX you don't.

Sources: Help Net Security, Tenable FAQ via Security Boulevard, Palo Alto Networks CVE-2026-123633 advisory, Sophos advisory, SOCRadar, SecurityOnline

nginxnginx2rootcve-2026-123007cve-2026-123633http2pan-ospanoramapalo-alto-networksf5supply-chain
All postsDiscuss on LinkedIn