Security

Nginx2Root: how to check and patch servers for CVE-2026-123007

Key takeaways

  • Five of ten Nginx flaws published together can lead to unauthenticated remote code execution in both free and commercial versions
  • Fixed releases are Nginx Open Source 1.31.9 and 1.30.7, and Nginx Plus 37.3.0.1 and 37.0.8.1 for the HTTP/2 flaw
  • Rapid7 says exploiting CVE-2026-123007 needs about 128 GB of HTTP/2 traffic, which limits practical attacks but is no reason to delay patching

After reading this guide, a sysadmin or security lead will be able to work out which Nginx servers are exposed to the Nginx2Root flaws, apply the fixed releases and reduce risk where patching has to wait.

Nginx, the open-source web server and reverse proxy that powers nearly 30% of websites according to W3Techs, has a batch of five memory corruption flaws, out of 10 vulnerabilities published together, that can lead to unauthenticated remote code execution. All five share the same high-severity CVSS score and each is a separate exploit path in both the commercial and free versions. The affected components include HTTP/2, HTTP/3, DNS resolution and mail proxy authentication.

Offensive security firm Xint chained a separate Linux kernel vulnerability with any of the Nginx flaws to gain root access. It calls the six together "nginx2root". Difficulty for this guide: moderate. Time: allow for an inventory and planning, plus your normal change window per server.

What you need before starting

  • An inventory of every host running Nginx: web servers, reverse proxies, load balancers, cache nodes, TCP/UDP proxies and mail proxies. Nginx often hides inside container images and appliances, so check those too.
  • Shell access or configuration management access to read each server's version and configuration.
  • The fixed versions to hand (listed below) and the F5 advisory for your product line.
  • A change window and a rollback plan. A worker-process crash is one of the flaw's stated outcomes, so test upgrades first.
  • No extra cost for Open Source users. Nginx Plus customers need access to F5's Plus repositories.

Step-by-step process

Step 1: Find every Nginx instance and its version

Run nginx -v on each host, and nginx -V to see build options. Record whether it is Open Source or Plus. Do not stop at public web servers; the flaws touch DNS resolution and mail proxy authentication, so internal proxies count.

Step 2: Check which exposed features you use

Read the active configuration (nginx -T). Look for HTTP/2, HTTP/3, the DNS resolver directive and any mail proxy blocks. The two flaws the researchers call the major ones map to specific features:

  • CVE-2026-123007 is an integer underflow. When HTTP/2 is enabled, it can make Nginx miscalculate how much data it can send to a client. F5 says an attacker could crash the worker process, corrupt its memory or potentially execute code remotely. F5 describes it as a data plane issue only, with no control plane exposure.
  • CVE-2026-113425 is a use-after-free affecting servers configured as mail proxies. It can enable remote code execution if Address Space Layout Randomization (ASLR), a protection that randomises where code sits in memory, is disabled or bypassed. Xint says it triggers during login and the attacker needs no valid credentials.

Prioritise any server with HTTP/2 plus TLS exposed to the internet, and any mail proxy.

Step 3: Upgrade to a fixed release

For CVE-2026-123007, F5 has fixes in:

  • Nginx Plus 37.3.0.1 and 37.0.8.1
  • Nginx Open Source 1.31.9 and 1.30.7

For CVE-2026-113425, the fixes are in Nginx Plus 37.3.0 and 37.0.8, and Nginx Open Source 1.31.9 and 1.30.7. On Open Source, 1.31.9 and 1.30.7 fix both flaws. On Plus, use 37.3.0.1 or 37.0.8.1 for the HTTP/2 flaw and 37.3.0 or 37.0.8 for the mail proxy flaw.

Step 4: Reload and verify

Run nginx -t to validate the configuration, then restart or reload. Confirm the new version with nginx -v, watch error logs for worker crashes, and re-scan your estate to confirm nothing was missed.

Step 5: Patch the kernel too

Xint's root access came from chaining a separate Linux kernel flaw with any of the Nginx flaws. Patching Nginx removes the entry point, but unpatched kernels leave the second half of the chain intact.

Common mistakes to avoid

  • Relying on an upstream proxy. Stephen Fewer of Rapid7 notes that a proxy between attacker and target may change how the traffic is transmitted and make the attack less likely to work. That is a side effect, not a control. Patch the backend regardless.
  • Assuming ASLR settles the mail proxy issue. The use-after-free depends on ASLR being disabled or bypassed. Verify it is on, but do not treat it as a substitute for the fix.
  • Patching only Open Source. Plus is affected too, and it has its own version numbers.
  • Ignoring the other flaws. Ten vulnerabilities were published together; five are memory corruption bugs with RCE potential.

Tips that make a difference

  • Xint says it found four of the other Nginx flaws in a fully automated scan without human guidance. Expect more automated discovery, so shorten your patch cycle for edge software rather than treating this as a one-off.
  • Watch for unexplained worker process restarts. A crash is a stated outcome of both flaws.
  • Compare this with other edge-software emergencies in your queue, such as PaperCut's pre-auth RCE chain, so you sequence work by exposure rather than by headline.

The UK picture

For UK organisations, an unpatched internet-facing server is a compliance question as well as a security one.

Next steps

  • Subscribe to F5's security advisories and add Nginx to your routine edge-patching schedule.
  • Review whether HTTP/3, mail proxy and DNS resolver features are enabled out of habit rather than need.
  • For related patching practice, see our checklist on N-able N-Central CVE-2026-86218.

Five Nginx flaws allow unauthenticated remote code execution across HTTP/2, HTTP/3, DNS resolution and mail proxy authentication. Fixes exist for both Open Source and Plus. Practical exploitation of the HTTP/2 flaw needs heavy traffic, but Rapid7's proof of concept shows it works. Patch Nginx and the kernel together.

You now have an inventory method, a feature-based risk check, the fixed version numbers, a verification routine and fallback mitigations. That is enough to close the Nginx2Root exposure on your estate within a normal change cycle.

Frequently asked questions

Which Nginx versions fix CVE-2026-123007?

F5 fixed it in Nginx Open Source 1.31.9 and 1.30.7, and in Nginx Plus 37.3.0.1 and 37.0.8.1.

Does the Nginx HTTP/2 flaw need authentication to exploit?

No. Rapid7 demonstrated unauthenticated remote code execution against a vulnerable server running HTTP/2 and TLS, though it needs a very large volume of traffic.

Is Nginx Plus affected as well as the free version?

Yes. The five memory corruption flaws are exploit paths in both the commercial and free versions of Nginx.

How is the Nginx mail proxy flaw triggered?

CVE-2026-113425 is a use-after-free triggered during login on servers configured as mail proxies. The attacker does not need valid credentials, according to Xint.

More from Future Technology HQ