Secure Cyber Blog

NGINX2Root: How SecureCyber Is Responding and What You Should Do Next

Written by SecureCyber | Nov 19, 2026, 3:25:13 PM

Nov 19, 2026

On November 18, F5 released fixes for two critical flaws in NGINX, CVE-2026-123007 and CVE-2026-123633, that let an attacker run code on the server without logging in. If you run NGINX with HTTP/2 enabled on an internet-facing server, patch now or turn HTTP/2 off until you can. Researchers are grouping these with three related NGINX flaws under the name nginx2root.

NGINX sits at the front door of many websites and APIs, handling encrypted traffic and routing it to the applications behind it. Both flaws are in how NGINX handles HTTP/2 and are rated Critical (CVSS 4.0: 9.2). Affected versions reach back to NGINX 1.9.5 from 2015 and include 1.31.8, the last release before the fix. Because one NGINX server often fronts several applications, a single compromise can expose all of them.

A public proof-of-concept exploit was released the same day, but as of November 18, no exploitation in the wild has been confirmed. That is good news, but it is not a reason to wait. NGINX also ships inside packaged products and appliances, so many organizations run it in places they have never inventoried.

What we have done and what we are still doing

The same day the fixes were released, our team ran its full vulnerability response across every client we protect:

  • Found NGINX wherever it runs, including copies hidden inside vendor products that standard inventories never see.
  • Separated real risk from noise, determining which installations can actually be attacked and which are reachable from the internet.
  • Hunted for exploitation across endpoint, forensic and network evidence. We found none.
  • Checked our own defenses to make sure nothing in our protection would let this attack slip through unnoticed.
  • Put new detections for this attack in place, now live across our monitoring.
  • Prepared a prioritized assessment for each affected client, covering their exposure and what to fix first. We are reaching out to each of them directly.

What the firewall can and cannot do

Patching NGINX is the fix. Network controls reduce exposure and buy time, and that is how we use them.

Our standard FortiGate build blocks all high and critical IPS signatures. When Fortinet releases a signature for an attack like this, it is blocked without a change on our side.

A CDN, WAF, or proxy that terminates HTTP/2 in front of NGINX may blunt these attacks, depending on how it is built. The public exploit will likely fail through a proxy, but that is no substitute for patching.

What you should do now

Find your NGINX. Inventory every NGINX instance, including copies inside appliances, containers, and vendor products, and check whether HTTP/2 is enabled.

Patch. Fixed builds are NGINX Open Source 1.30.7 and 1.31.9, and NGINX Plus 37.0.8.1 and 37.3.0.1. NGINX Plus R34 through R36 has no fix listed, so move to a fixed 37.x build. For NGINX bundled in another product, use the fixed build named in that vendor's advisory.

If you cannot patch right away, turn off HTTP/2 by setting http2 off; and removing http2 from listen directives. It is a temporary workaround that closes the attack path for both flaws until you can update. Services that require HTTP/2, such as gRPC, will be affected.

Start with internet-facing systems. If you publish a site or API through a firewall we manage, tell us so we can prioritize it.

If you are a SecureCyber customer with questions about your exposure, reply on your ticket or reach out to your account team. Our work on this is ongoing, and we are here to help you through it.