Incident sheet · /security

Filed
Read
4 min · 769 words
Severity
Routine

Five critical Nginx flaws patched after Linux root exploit chain

Five patched Nginx CVEs, including a 9.2-rated HTTP/2 flaw, can chain with an unpatched Linux kernel bug to turn a worker process into host root on affected systems.

Nginx servers rootable through critical flaws, unpatched Linux kernel bug
FeedNginx servers rootable through critical flaws, unpatched Linux kernel bug — blickpixel / pixabay

Event log

  1. F5 patched five Nginx vulnerabilities, each rated 9.2 under CVSS 4.0.
  2. CVE-2026-123007 enables unauthenticated command execution over HTTP/2, and Nginx releases 1.9.5 through 1.31.8 contain the vulnerable code.
  3. The chained Linux SCTP flaw dates to Linux 4.15 from 2018 and had no patch at disclosure.
  4. Rapid7's proof-of-concept exploit requires about 128 GB of HTTP/2 traffic over one connection.
  5. Nginx appears on 29.7 per cent of websites with identifiable server software.

By Amara Osei

Five critical Nginx vulnerabilities each scored 9.2 under the Common Vulnerability Scoring System 4.0, and AI security platform Xint chained the most serious with an unpatched Linux kernel defect to reach host root.

Xint disclosed the set as NGINX2Root and said every vulnerability has a proven exploit. F5, which develops Nginx, issued the fixes. CVE-2026-123007, the most serious issue, lets an unauthenticated attacker run commands on a server through Nginx's HTTP/2 support.

The exposure is material because Nginx runs on 29.7 per cent of websites where W3Techs can identify the server software—roughly three in every 10. Installations also sit in front of other applications as reverse proxies and load balancers, and act as gateways for traffic between services.

The immediate vendor response covers Nginx, but not the separate Linux kernel weakness used for privilege escalation.

What does the HTTP/2 flaw allow?

HTTP/2 lets browsers and servers exchange many requests over a single connection. Its flow-control mechanism tells each side how much data the other is ready to receive.

CVE-2026-123007 lets an attacker push Nginx's running allowance past its limit. The server then copies data beyond the memory reserved for it, creating exploitable memory corruption.

Xint said: “Every official release from 1.9.5 through 1.31.8 contains the vulnerable code.”

Xint described three other flaws as affecting Nginx only when it forwards requests to backend servers, and the fourth as residing in the mail proxy.

In plain terms: a reachable HTTP/2 service can offer an unauthenticated route to command execution.

How did a worker process reach host root?

On its own, CVE-2026-123007 grants only the privileges of an Nginx worker process, which normally runs under a restricted account. It does not grant root access.

To elevate those privileges, Xint exploited a Linux kernel flaw in the handling of the Stream Control Transmission Protocol, or SCTP. The protocol serves mainly as a signalling mechanism in telecommunications networks.

The kernel flaw dates back to Linux 4.15, released in 2018. In Xint's tests, a compromised Nginx worker reliably gained root on the host, including from inside a Docker container. The demonstrated chain therefore crossed the container boundary.

At disclosure, the kernel flaw had no CVE identifier and no patch. Xint withheld most technical details until a fix became available.

Xint advised blocking the SCTP module through a configuration file, but noted that this neither unloads a module already running nor disables SCTP compiled into the kernel.

In plain terms: the web-server bug opens the door, while a separate kernel defect supplies the route to full host control.

Who has produced working exploit code?

Xint was not alone in finding the HTTP/2 flaws. Wiz said researchers from Wiz, Rapid7, Ikotas Labs, Metnir and Xint independently found the two bugs at roughly the same time.

Xint said its automated platform found four of the five vulnerabilities without human guidance. That puts most of the disclosure within the reach of repeatable automated testing.

On disclosure day, Rapid7 published a proof-of-concept exploit for CVE-2026-123007. It requires about 128 gigabytes of HTTP/2 traffic over one connection.

Stephen Fewer, senior principal security researcher at Rapid7, wrote: “Alternative RCE exploitation strategies may be viable, but none are currently known.”

Wiz has not released its exploits, but said its code achieved reliable remote code execution against Nginx serving only static files.

In a November 18, 2026 post, Wiz's Nir Ohfeld described CVE-2026-123633 and CVE-2026-123007 as exploitable memory corruptions requiring HTTP/2. He said the team defeated ASLR and achieved reliable remote code execution against Nginx with no backend or third-party modules.

No exploitation in the wild had been reported when the disclosure was written.

In plain terms: public proof-of-concept code lowers the barrier to attack, although no active exploitation had been reported.

What should operators change now?

As a stopgap for the two HTTP/2 vulnerabilities, Xint suggested switching HTTP/2 off. Browsers would fall back to HTTP/1.1, but services that depend on HTTP/2, including applications communicating through Google's gRPC framework, would stop working.

F5's patches cover the five Nginx vulnerabilities, while the Linux kernel bug had no patch at disclosure. Defenders therefore face two control points: deploy the Nginx fixes and assess SCTP exposure while the kernel issue remains unresolved.

In plain terms: the web-server fixes are available, but operators still need a separate response to the kernel weakness and any dependency on HTTP/2.

via itnews.com.au (Source)

Filed under

  • nginx
  • cve-123007
  • http-2
  • linux-kernel
  • remote-code-execution
Share this article:

More from Amara Osei

Amara Osei

Show full bio

Correspondent covering regulation, policy and their impact on enterprise information technology and the leaders who run at CIO Monitor.

188 articles

The newsroom digest

One email a day with the stories that matter. No noise.

By subscribing you agree to the privacy policy.

Cross-references

‹ Previous articleNext article ›