SquishPixel Blog · Site security · WordPress · Hosting and CDNs

nginx2root: five nginx flaws fixed, WordPress servers need patching and a restart

According to DEV Community, researchers at Xint named five nginx memory-safety bugs "nginx2root". They were fixed on 18 November 2026 in nginx 1.31.9 (mainline) and nginx 1.30.7 (stable). Every release up to and including 1.31.8 is affected where the relevant feature is in use.

The most serious is CVE-2026-123007, a memory corruption bug in HTTP/2 flow control. F5 scores it 9.2 Critical. It can let an unauthenticated attacker run code on the server over HTTP/2, which most HTTPS WordPress sites on nginx have switched on. The other four bugs involve HTTP/2 with upstream requests, the resolver, HTTP/3 and the mail proxy. Which one applies depends on your configuration.

The code would run as the nginx worker, an unprivileged user. On its own that could still expose wp-config.php or allow files to be planted in uploads. Xint chained it with a Linux kernel bug in SCTP networking code to reach root. At publication that kernel bug had no CVE number and no fix, so the article advises blocking the SCTP module on the host.

The article says no attacks in the wild had been reported on release day, and CISA had not listed the CVE in its Known Exploited Vulnerabilities catalogue. Proof-of-concept code is public on GitHub, though it only demonstrates an attack on a freshly started Docker container on the same machine.

The fix depends on how you host. Managed hosts should patch for you, so ask them to confirm. Forge warns that its automatic security updates do not update nginx. Ubuntu shipped fixes on 19 November. On that date Debian's tracker showed a fix only in unstable. A reload is not enough: nginx must be restarted so the patched binary runs. If you cannot patch at once, turning off HTTP/2 and HTTP/3 reduces exposure.

Why it matters

WordPress itself is not at fault, so updating core, plugins or themes does nothing here. The flaw sits in the web server in front of PHP. Sites can look fully up to date at the WordPress level and still be exposed.

The bug is in a feature that is on by default for most HTTPS sites, and the details are public. Owners of a VPS or Docker stack are on their own, because nobody else will patch it. Sites behind a CDN are only protected if the origin accepts connections from the CDN alone. Images that bundle their own nginx are easy to forget.

Source: DEV Community. This brief summarises their reporting; read the original for the full detail.