The short answer

On November 18, 2026, F5 and the NGINX project disclosed five memory-safety vulnerabilities in NGINX, nicknamed NGINX2Root by the Xint researchers who reported them. The most serious, CVE-2026-123007, affects any NGINX server with HTTP/2 enabled, and an unauthenticated attacker could crash it or potentially run code as the NGINX worker process. Fixes shipped the same day in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). Researchers say no in-the-wild exploitation has been reported yet, but they have working exploits, so patch soon. If your WordPress site runs on NGINX, ask your host whether they have applied the fix, or check yourself. If you cannot patch right away, turning HTTP/2 off blocks the two most reachable bugs.

A concerned man rests a hand on his forehead and looks at a computer screen, holding his glasses in the other hand.

What was disclosed

NGINX is one of the most widely used web servers, and many WordPress hosts run it directly or in front of Apache or PHP-FPM. On November 18, F5 published five CVE records and the NGINX project released fixes. All five have the same scores: 8.1 (High) on CVSS 3.1 and 9.2 (Critical) on CVSS 4.0, according to Sysdig and Sophos. The NGINX project itself labels CVE-2026-123007 and CVE-2026-113425 as "major" and the other three as "medium".

Each flaw lets an unauthenticated attacker over the network corrupt memory in an NGINX worker process. F5 describes the impact as a worker crash or memory corruption, with code execution possible where ASLR (a memory protection) is off or can be bypassed. CERT-EU summarizes it as unauthenticated code execution with the privileges of the NGINX worker process.

The five CVEs

CVEWhat it isOnly matters ifVulnerable (Open Source)
CVE-2026-123007HTTP/2 flow control: integer underflow, heap overflowHTTP/2 is enabled1.9.5 to 1.31.8
CVE-2026-123633HTTP/2 use-after-freeHTTP/2 is on and requests are proxied to a backend1.19.7 to 1.31.8
CVE-2026-123634Resolver use-after-freeA request-based proxy_pass, a resolver, and a mirror or SSI subrequest are used0.6.18 to 1.31.8
CVE-2026-121810HTTP/3 (QUIC) use-after-freeHTTP/3 is on and requests are proxied to a backend1.25.0 to 1.31.8
CVE-2026-113425Mail proxy use-after-freeNGINX is a mail proxy with auth_http0.5.33 to 1.31.8

Version ranges are from nginx.org. For a typical WordPress site, the one to care about is CVE-2026-123007, because HTTP/2 is common on public HTTPS sites. Sysdig reports that researchers could reach the vulnerable code just by serving ordinary static files, with no backend application or add-on module needed. The mail proxy bug is unlikely to apply to a normal website.

Is this being exploited?

Not as far as anyone has reported. CERT-EU says no exploitation in the wild has been reported, and Sysdig says there is no public proof-of-concept as of its November 19 post. As of the CISA Known Exploited Vulnerabilities catalog release on November 18, none of the five CVEs was listed. But this is not a "wait and see" situation. Xint and Wiz both say they built working exploits that get around ASLR, and several teams found the HTTP/2 bug independently. Xint also chained it with a separate Linux kernel flaw (in SCTP, with no CVE or patch yet) to get root on the host, including from inside a Docker container. Plan to patch now rather than after an exploit appears.

What to do if you run WordPress on NGINX

1. Find out whether you use NGINX

If you pay for managed WordPress hosting, your host runs the server and the fix is theirs to apply. Ask them in plain terms: "Have you applied the NGINX fixes for CVE-2026-123007 (NGINX2Root)?" Many hosts will already have a notice posted. If you manage your own server or VPS, keep reading.

2. Check your version, with one caveat

On the server, run nginx -v. You want 1.30.7 or newer on the stable line, or 1.31.9 or newer on mainline. NGINX Plus customers should be on 37.3.0.1 or 37.0.8.1, per Sysdig.

The caveat: Ubuntu and Debian often fix security bugs without changing the version number. Ubuntu 24.04 ships 1.24.0, Ubuntu 22.04 ships 1.18.0, Debian 12 ships 1.22.1 and Debian 13 ships 1.26.3, and those will still say the old number after they are fixed. As of November 18, Sysdig reports Debian and Ubuntu list every supported release as vulnerable with no fixed package yet. So for distribution packages, watch your distribution’s security notice and install the new package revision when it appears, rather than trusting the version number alone.

3. Patch, then restart

Update NGINX through your package manager or the NGINX.org repository, then restart NGINX instead of just reloading it. A reload leaves existing connections on the old worker processes. If NGINX runs in a Docker container, rebuild the image on a fixed version and redeploy, because patching the host does not change a running container.

4. If you cannot patch today, turn off HTTP/2

This is the stop-gap both CERT-EU and Sysdig describe. On NGINX 1.25.1 or newer, add http2 off; in each affected server block and remove http2 from the listen line. On 1.9.5 through 1.25.0, remove http2 from listen. This blocks CVE-2026-123007 and CVE-2026-123633, and your site keeps working over HTTP/1.1, just somewhat slower. Turn it back on after you upgrade. It does not cover the HTTP/3, resolver or mail proxy bugs, which only apply if you use those features.

5. Look for signs of trouble

Worker crashes are the most visible clue. Search the NGINX error log for worker process and exited on signal. CERT-EU notes this is not proof of a break-in, only a sign of attempts, so also check for unexpected processes started by the web server user. If anything looks wrong, preserve the logs before cleaning up.

6. Other things to know

  • The Kubernetes ingress-nginx project was archived in March 2026 and will not ship these fixes, so plan a migration.
  • Software built on NGINX code, such as OpenResty, Tengine and Angie, was not named in the advisories. Check with those projects.
  • The same release also fixes five other NGINX issues, ten in total, so upgrading is worth doing even if your configuration avoids the five above.

What it means for a small business

A web server flaw is not a WordPress flaw, so updating plugins will not fix it. The fix lives on the server, which is why it often falls between the site owner and the host. The practical step is a short, written question to your host or developer, and a note on when it was answered. If nobody owns that question for your site, that is the real gap to close. Our WordPress Maintenance plans include server and update monitoring, and WordPress Security reviews cover hosting configuration. If a site already looks compromised, WordPress Rescue handles cleanups.

FAQ

What is NGINX2Root?

NGINX2Root is the name the Xint research team gave to five NGINX memory-safety vulnerabilities, plus a separate Linux kernel flaw they chained with them to gain root. F5 and the NGINX project disclosed the five NGINX CVEs on November 18, 2026.

Which NGINX versions fix the NGINX2Root flaws?

NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). For NGINX Plus, Sysdig lists 37.3.0.1 and 37.0.8.1 as the fixed releases.

Is CVE-2026-123007 being exploited?

No in-the-wild exploitation has been reported as of November 19, 2026, and it was not in the CISA Known Exploited Vulnerabilities catalog on November 18. Researchers have working exploits, though, so patching soon is advised.

How do I check which NGINX version my server runs?

Run nginx -v on the server. On Ubuntu and Debian, the version number may not change when a security fix is installed, so check your distribution's security notice and package revision as well.

Can I mitigate this without upgrading?

Turning off HTTP/2 (http2 off; on 1.25.1 and newer, or removing http2 from listen on older versions) blocks CVE-2026-123007 and CVE-2026-123633. The other three need HTTP/3, a resolver with request-based proxying, or the mail proxy, so removing those features covers them.

Do I need to do anything if my WordPress host manages the server?

Yes, ask. The host applies the fix, but you should confirm it has been applied and ask when. Updating WordPress plugins does not fix a web server flaw.

Sources

  1. nginx.org, "nginx security advisories" (versions and severity). https://nginx.org/en/security_advisories.html
  2. F5, advisory K000164058 (vendor advisory, as cited by CERT-EU; page requires JavaScript). https://my.f5.com/manage/s/article/K000164058
  3. CERT-EU Security Advisory 2026-022, "Critical vulnerabilities in Nginx" (November 18, 2026). https://www.cert.europa.eu/publications/security-advisories/2026-022
  4. Xint, "NGINX2Root: New Remote Code Execution Vulnerabilities in nginx Require Urgent Patching" (November 18, 2026). https://xint.io/blog/nginx2root-remote-code-execution
  5. Sysdig Threat Research Team, "NGINX2Root: Five RCE bugs in NGINX, a Linux kernel path to root, and how to detect exploitation" (November 19, 2026). https://www.sysdig.com/blog/nginx2root
  6. Sophos advisory, "NGINX Vulnerabilities - nginx2root" (November 18, 2026). https://www.sophos.com/en-us/security-advisories/sophos-sa-20261118-nginx2root
  7. Rapid7, "CVE-2026-123007: critical NGINX HTTP/2 integer underflow leads to RCE (fixed)". https://www.rapid7.com/blog/post/ve-cve-2026-123007-critical-nginx-http-2-integer-underflow-leads-to-rce-fixed/
  8. CISA, Known Exploited Vulnerabilities Catalog (checked against the November 18, 2026 release). https://www.cisa.gov/known-exploited-vulnerabilities-catalog