On 18 November 2026 the nginx project released emergency updates that fix ten security flaws. Five of them, which the research firm Xint named NGINX2Root, can let an attacker with no login run code on the web server. The one with the widest reach needs only HTTP/2 to be switched on.
Many UK websites sit behind nginx because a host or a developer chose it. Most owners therefore need one answer first: who patches the server, and have they done it?
The answer in brief
- Version 1.31.9 of nginx fixes all ten flaws listed in nginx’s security advisories. Version 1.30.7 fixes the nine that affect the stable branch, including all five NGINX2Root flaws.
- The widest flaw, CVE-2026-123007, is in HTTP/2 handling. It affects every version from 1.9.5, released in 2015, to 1.31.8.
- No attacks have been reported. Rapid7 has published a proof of concept that works under lab conditions.
- Ubuntu, Debian, Amazon Linux 2023, AlmaLinux and Alpine have fixed packages. Red Hat Enterprise Linux and SUSE Linux Enterprise do not.
- If you cannot update, turning HTTP/2 off blocks two of the five flaws.
- If someone else hosts your site, ask which nginx package is running and whether it contains the fix.
- Apache has a separate HTTP/2 flaw, CVE-2026-119618, fixed in Apache HTTP Server 2.4.71.
What is NGINX2Root?
NGINX2Root is Xint’s name for five memory corruption flaws in nginx that an attacker can reach over the network without logging in. Xint’s write-up says each can lead to code running on the server. F5, the company behind nginx, scores each at 8.1 under CVSS v3.1 and 9.2 under CVSS v4.0, according to Censys.
If the table extends beyond the screen, scroll sideways to view all columns.
| CVE | nginx’s rating | Flaw | Affected versions | In scope if you use |
|---|---|---|---|---|
| CVE-2026-123007 | nginx’s ratingMajor | FlawMemory corruption in HTTP/2 flow control | Affected versions1.9.5 to 1.31.8 | In scope if you useHTTP/2 |
| CVE-2026-123633 | nginx’s ratingMedium | FlawUse-after-free in HTTP/2 | Affected versions1.19.7 to 1.31.8 | In scope if you useHTTP/2 with requests passed to a backend, when the worker runs short of connections |
| CVE-2026-123634 | nginx’s ratingMedium | FlawUse-after-free in the resolver | Affected versions0.6.18 to 1.31.8 | In scope if you useA resolver, a proxy_pass destination taken from the request, and subrequests such as mirror |
| CVE-2026-121810 | nginx’s ratingMedium | FlawUse-after-free in HTTP/3 | Affected versions1.25.0 to 1.31.8 | In scope if you useHTTP/3 with requests passed to a backend, when the worker runs short of connections |
| CVE-2026-113425 | nginx’s ratingMajor | FlawUse-after-free in the mail proxy module | Affected versions0.5.33 to 1.31.8 | In scope if you useMail proxy with proxy on and auth_http |
CVE-2026-123007 is the one that reaches most sites. It sits in nginx’s own HTTP/2 code, so nothing behind nginx has to be at fault. Tenable reports that Wiz confirmed code execution on a server that did nothing but serve static files.
The same releases fix more flaws: five in 1.31.9, of which four also affect the stable branch and are fixed in 1.30.7. The most serious of those, CVE-2026-118899, is an infinite loop while reading a request body over TLS 1.3, which nginx also rates major.
Why does the name say root?
The root part comes from a second, separate flaw in the Linux kernel. Code run through the nginx flaws lands in an nginx worker process, which normally has limited privileges. Xint chained them with a flaw in the kernel’s SCTP networking code to go from the worker to root, including out of a Docker container.
That kernel flaw has no CVE and no patch, and Xint is withholding most of the details until a fix exists.
Is my website affected?
Your site is affected if an unpatched nginx from 1.9.5 to 1.31.8 handles its traffic with HTTP/2 enabled, whether nginx is the web server itself or a proxy in front of something else. The other four flaws need HTTP/3, a mail proxy or particular proxy settings, as the table shows.
Four things make this harder to answer than it sounds:
- The version number can mislead. Linux distributions add security fixes to older nginx versions without changing what
nginx -vprints. Compare the full package version with the distribution’s advisory. - A CDN may or may not cover you. Cloudflare says it updated its own edge before the disclosure, so a site reachable only through its HTTP proxy is shielded while you patch. A server that can also be reached directly is still exposed, Precursor Security notes.
- Appliances bundle nginx. Synology has confirmed that DSM and BeeStation OS are affected by CVE-2026-123007, GBHackers reports.
- Kubernetes needs a separate check. The community ingress-nginx controller is retired and will not be patched. Setting
use-http2: "false"is the stopgap.
Is NGINX2Root being exploited?
No attacks have been reported, and none of the flaws is in CISA’s Known Exploited Vulnerabilities catalogue. A working proof of concept is public, though. Rapid7 published one for CVE-2026-123007 on the day of the disclosure.
Rapid7’s exploit has limits. It needs roughly 128 GB of HTTP/2 traffic, a way round address randomisation and a memory routine found on x86-64 processors with AVX-512, The Hacker News reports. A slow connection, or a proxy in front of nginx that handles HTTP/2 itself, tends to defeat it. Xint and Wiz say they have exploits of their own and are not releasing them.
Fake NGINX2Root exploits are already on GitHub, according to Precursor Security. Do not download one to test your own server.
None of this is a reason to wait. Apache’s HTTP/2 flaw, covered below, went from patch to exploitation warning in six days.
Which nginx versions and packages are fixed?
Version 1.30.7 on nginx’s stable branch and 1.31.9 on its mainline branch both fix NGINX2Root, but some Linux distributions have not shipped the fixes yet. Where your nginx comes from decides what you can do. PatchMon’s distribution list and Precursor Security’s NGINX2Root tracker follow each source.
If the table extends beyond the screen, scroll sideways to view all columns.
| Source of your nginx | Status |
|---|---|
| nginx.org packages | StatusFixed in 1.30.7 and 1.31.9 |
| NGINX Plus | StatusFixed in 37.0.8.1 and 37.3.0.1. Releases R34 to R36 get no fix |
| Official Docker images | StatusFixed tags published. Running containers keep the old build until redeployed |
| Ubuntu | StatusFixed by USN-9159-1 on 19 November 2026 (24.04: 1.24.0-2ubuntu7.20; 22.04: 1.18.0-6ubuntu14.23). 20.04 and older need Ubuntu Pro |
| Amazon Linux 2023 | StatusFixed in 1.30.7-1.amzn2023.0.1 |
| AlmaLinux 8, 9 and 10 | StatusFixed on supported module streams |
| Alpine | StatusFixed on 3.22, 3.23, 3.24 and edge, according to Alpine’s security tracker |
| Debian 12 and 13 | StatusFixed in 1.22.1-9+deb12u11 on Debian 12 and 1.26.3-3+deb13u11 on Debian 13, according to Debian’s security tracker |
| Red Hat Enterprise Linux, SUSE Linux Enterprise, Rocky Linux | StatusNot fixed |
| Community ingress-nginx for Kubernetes | StatusRetired. Will not be patched |
Patching across the internet is slow. Censys counted about 8.8 million internet-facing services on an affected version with HTTP/2 enabled on 19 November 2026, the day after the release, according to Precursor Security’s tracker. About 425,000 had been fixed or had HTTP/2 turned off by then.
What should you do now?
Update nginx and restart it, or get confirmation from whoever runs your server that they have. In order:
- Find out who runs the server. On shared or managed hosting it is the host. On a cloud server or VPS it is usually you or your developer.
- Check the package, not the version banner. Ask for, or look up, the full package version and compare it with the distribution’s security advisory.
- Update. Install 1.30.7 or 1.31.9 from nginx.org, or the distribution’s fixed package. For containers, pull the new image and redeploy.
- Restart, do not reload. A reload leaves the old program running. Use a full restart or a supported live binary upgrade.
- Block SCTP where it is not needed. Add
install sctp /bin/falseto a.conffile in/etc/modprobe.d/. Runlsmod | grep sctpfirst, because this does not unload a module that is already loaded. It also has no effect where SCTP is built into the kernel. - Get it in writing. If a host or agency patches for you, ask them to confirm the fixed package by name. A version number alone does not prove it.
What can you do if you cannot update nginx yet?
Turn HTTP/2 off, which blocks CVE-2026-123007 and CVE-2026-123633 and leaves the other three flaws open. This is the position for anyone on Red Hat Enterprise Linux, SUSE Linux Enterprise or Rocky Linux packages.
- HTTP/2. On nginx 1.25.1 and later, set
http2 off;in each affectedserverblock and removehttp2from itslistenlines. On older versions, removehttp2from thelistenline. Native gRPC stops working without HTTP/2. - Check it worked. Run
openssl s_clientwith-alpn h2against the server itself, not a CDN address in front of it. The output should no longer showALPN protocol: h2. - HTTP/3. Remove the QUIC listeners and clear the
Alt-Svcheader. - Mail proxy. Bind its listeners to loopback or restrict them with a firewall.
- Resolver flaw. Use fixed upstream groups in place of a
proxy_passbuilt from variables, and dropmirrorwhere it is not needed.
Xint advises against treating HTTP/2 off as a complete answer, and we agree. It buys time on two flaws and nothing on the rest.
How would you know if a server had been attacked?
There is no single reliable sign, and a clean access log does not rule an attack out. Luxembourg’s CIRCL lists four things to look for, as reported by The Hacker News:
- nginx worker processes starting programs they should not;
- workers exiting abnormally or leaving core dumps;
- long-lived HTTP/2 connections with heavy inbound traffic and few logged requests;
- unusual outbound connections or DNS lookups from the server.
Does Apache have the same problem?
Apache HTTP Server has a separate HTTP/2 flaw, CVE-2026-119618, which was fixed in version 2.4.71 on 11 November 2026. It is a race condition in the mod_http2 module that can corrupt memory and lead to remote code execution. Apache’s vulnerability list rates it critical and gives the affected range as 2.4.55 to 2.4.70.
This one comes with an exploitation warning. Singapore’s Cyber Security Agency published alert AL-2026-164 on 17 November 2026 under a headline saying attackers are exploiting the flaw. The alert’s own detail is more careful: it says the flaw is reportedly being exploited and that proof-of-concept code is public. It names no victims, and CISA has not listed the flaw as exploited.
Guardz’s analysis adds that the public proof of concept shows memory corruption in a lab and not working code execution. We would still treat the warning as reason enough to patch.
The fix follows the same pattern as nginx. Upgrade to 2.4.71 or the distribution’s fixed package, or set Protocols http/1.1 as a stopgap. A server that only speaks HTTP/1.1 is not affected.
Why are so many web server flaws being found at once?
Automated code analysis is finding flaws that sat unnoticed for years. Apache credits Anthropic’s OSS Scanner with the first report of CVE-2026-119618, on 26 October 2026, eight days before two Google researchers reported it independently. Xint says an automated scan found four of the five NGINX2Root flaws without human guidance.
The volume shows in nginx’s own record. Xint counts 26 nginx security advisories in 2026 before this release, against two in the whole of 2025.
We have seen the same pattern in PHP. Our PHP2Shell news post covers AI-assisted research that made a PHP bug dating from 2012 practical to exploit, and our Black October guide sets out how attackers are using AI.
For a website owner, the practical change is the pace. Software that could go months between security updates now needs someone watching it every week. The same week brought fixes for WordPress core and PHP, which we cover in WordPress 7.1.5 and PHP security updates.
If you are not sure who patches your server, or whether they have, talk to AIWIZ.