deniz.in

Markets

Weather

Loading weather

· via dev.to (home feed)

Five nginx flaws including unauthenticated HTTP/2 code execution patched in 1.31.9 and 1.30.7

Five nginx memory-safety bugs dubbed nginx2root were fixed on 18 November 2026; the worst allows unauthenticated code execution over HTTP/2, and a Linux kernel flaw can chain it to root.

Five nginx flaws including unauthenticated HTTP/2 code execution patched in 1.31.9 and 1.30.7

nginx2root covers five memory-safety bugs

On 18 November 2026 nginx shipped fixes for five memory-safety vulnerabilities that researchers at Xint have collectively named nginx2root, according to a technical guide published on dev.to. The patches landed in version 1.31.9 of the mainline branch and 1.30.7 of the stable branch, and every release up to and including 1.31.8 is affected where the relevant feature is in use. Xint reported the issues to F5, which maintains nginx, and published its analysis the same day the updates arrived.

The most severe issue, CVE-2026-123007, is a memory corruption flaw in HTTP/2 flow control that has been present since version 1.9.5 shipped in 2015. F5 describes it as a heap buffer overflow that typically crashes the worker process, but which can allow code execution where address space layout randomisation is disabled or can be defeated. According to The Hacker News, researchers at Wiz managed to bypass ASLR in their testing, and Xint needed nothing more than a port reachable over HTTP/2, with no authentication required. F5 scores the bug 9.2 Critical under CVSS 4.0 in its NVD entry, while the nginx.org advisory rates it Major.

The other four issues in the set:

  • CVE-2026-123633, a use-after-free in HTTP/2 that requires requests passed to an upstream while workers run low on worker_connections, first affected in 1.19.7.
  • CVE-2026-123634, a use-after-free in the resolver, triggered by a proxy_pass host built from variables combined with an SSI or mirror subrequest, since 1.13.4.
  • CVE-2026-121810, a use-after-free in HTTP/3 (QUIC) when requests go to an upstream, since 1.25.0.
  • CVE-2026-113425, a use-after-free in the mail proxy where proxy and auth_http are both enabled, dating back to 0.5.15.

The same releases also close five further issues outside the nginx2root set, including an endless loop when reading request bodies over TLS 1.3 (CVE-2026-118899) and a buffer overflow involving alias and try_files (CVE-2026-125283).

From worker process to root

Code execution through the HTTP/2 bug lands in an unprivileged nginx worker, typically running as www-data or nginx. On a WordPress server that alone is enough to read wp-config.php and its database credentials, or to place files in a writable uploads directory, the dev.to guide points out.

The second half of the chain is a use-after-free in the Linux kernel's SCTP networking code, which security firm Aikido says has been present since Linux 4.15. Xint reportedly used it to climb from the nginx worker to root on the host, and found that the path also works from inside a Docker container. At the time the research was published there was no CVE number and no kernel patch for that bug, which makes disabling SCTP a worthwhile defensive measure.

No attacks had been reported in the wild when the disclosure went out, and CISA had not added the issue to its Known Exploited Vulnerabilities catalogue. Proof-of-concept code is already public on GitHub, although its notes state that it only demonstrates the attack against a freshly started container on the same machine.

Who is exposed and who patches

WordPress itself contains no bug here: the flaws sit in the web server in front of PHP, so updating plugins, themes or core achieves nothing. The dev.to guide notes that nearly every HTTPS WordPress site on nginx runs HTTP/2, and because fastcgi_pass, the usual way nginx hands PHP requests to PHP-FPM, uses the same machinery as upstreams, a standard WordPress server falls within scope for both HTTP/2 bugs.

Responsibility depends on the hosting arrangement. Managed WordPress hosts handle the nginx update themselves. Control panels differ: Laravel Forge warns that its automatic security updates do not cover nginx because the package comes from a separate repository, and older Forge servers relied on a PPA that has since been removed. Operators of their own VPS or Docker stacks have to patch alone. Sitting behind Cloudflare or another CDN only helps if the origin accepts connections from the CDN's addresses alone; an origin that answers on port 443 from anywhere can be reached directly.

Older distributions are a particular problem. According to Forge, nginx.org no longer builds packages for Ubuntu 20.04 and earlier, and the newest one available there, 1.27.5, remains vulnerable. Ubuntu's own nginx package is fixed for 16.04, 18.04 and 20.04, but only through Ubuntu Pro, which is free for up to five machines.

Why it matters

The headline bug is unauthenticated, reachable over a protocol that most HTTPS deployments on nginx have enabled, and has been quietly present for roughly a decade. Patched releases exist and the fix is a routine version bump on supported systems, but many deployments, from managed panels to legacy Ubuntu servers, will not receive it automatically. With a public write-up, proof-of-concept code on GitHub, and an unpatched kernel bug that completes the path to root, operators should verify their nginx version now and treat anything below 1.30.7 or 1.31.9 as exposed.

  • #nginx
  • #security
  • #vulnerabilities
  • #http2
  • #web-servers

Related posts