On Nov 18, F5 disclosed five flaws in nginx, the web server that sits in front of most Laravel apps. Researchers at Xint, who found them, call the set nginx2root. F5 rates all five 9.2 on CVSS v4.0. The worst, CVE-2026-123007, has been in nginx's HTTP/2 code since version 1.9.5, released in 2015.
Your application code plays no part here. nginx reads the request before PHP sees it, so a clean Laravel app behind an unpatched nginx is as exposed as any other site on that server.
The fix itself is a package update and a restart. The work is finding every nginx you run, including the ones that your operating system's updates never touch, and checking that the patched version is the one actually running.
The five flaws, and what each one needs
Each flaw sits in a different part of nginx, so whether it reaches you depends on what your configuration turns on.
| CVE | Part of nginx | If you cannot patch today |
|---|---|---|
| CVE-2026-123007 | HTTP/2 | Turn off HTTP/2 on your listen lines |
| CVE-2026-123633 | HTTP/2, when proxying to a backend | Same as above |
| CVE-2026-121810 | HTTP/3 (QUIC) | Remove the QUIC listeners |
| CVE-2026-123634 | The resolver, when a proxied backend's name contains variables | Use a fixed upstream group; turning off mirror alone is not enough |
| CVE-2026-113425 | Mail proxy | Bind it to localhost or firewall it |
Sources: Tenable's nginx2root FAQ and Qualys.
Most sites served over HTTPS have HTTP/2 turned on, so the first row is the one that applies to nearly everyone. Turning HTTP/2 off is a valid stopgap: browsers fall back to HTTP/1.1 and pages load somewhat slower. It does not cover the other three flaws, so it buys time rather than replacing the patch.
How urgent it is
Rapid7 published working exploit code for CVE-2026-123007. It is hard to use: it needs about 128 GB of HTTP/2 traffic and a separate way around a memory protection called ASLR. As of Nov 19, Tenable reported no attacks in the wild, and the flaws were not on CISA's list of known exploited vulnerabilities.
That does not make it a job for next month. Public exploit code tends to get easier to use, and the risk grows over time.
Exploit code is public. The hard parts of an exploit tend to get solved once the code is out.
Containers do not contain it. Xint chained the nginx flaw with an unpatched Linux kernel bug in SCTP, a network protocol few web servers use, and reached root on the host from an nginx worker inside a Docker container. The kernel bug has no fix yet. If your servers do not use SCTP, block its kernel module.
Old branches get nothing. The fixed upstream releases are 1.30.7 (stable) and 1.31.9 (mainline). nginx branches before 1.30 get no upstream release. On those, the fix comes from your Linux distribution or not at all.
Which package fixes it on your server
Linux distributions backport the fix into the nginx version they ship, so the version number does not change. On a patched Ubuntu 22.04 server, nginx -v still says 1.18.0. Check the package revision instead: dpkg -l nginx-core (or dpkg -l nginx).
| Ubuntu release | First fixed nginx package |
|---|---|
| 26.04 LTS | 1.28.3-2ubuntu1.13 |
| 24.04 LTS | 1.24.0-2ubuntu7.20 |
| 22.04 LTS | 1.18.0-6ubuntu14.23 |
| 20.04 LTS and older | Ubuntu Pro (ESM) builds only |
From Ubuntu's CVE page (USN-9159-1, Nov 19). A later notice added fixes for other nginx flaws, so install the newest package your release offers, not the minimum above.
flowchart LR
A[Find every nginx] --> B{Installed by apt?}
B -- Yes --> C[Check package source]
C --> D[Upgrade and restart]
B -- No --> E{Docker image?}
E -- Yes --> F[Pull image, recreate]
E -- No --> G[Ask the vendor]
D --> H[Confirm running version]
F --> H
How to patch without breaking the site
List every place nginx runs: web servers, staging, load balancers, and nginx inside Docker containers. A container's nginx is not updated by the host's package manager.
Check where the upgrade would come from before you install it. Run
apt-cache policy nginxand read theCandidateline. If it points to a third-party repository built for a different release of your operating system, fix that repository first.Upgrade nginx and its modules together:
apt install --only-upgrade 'nginx*' 'libnginx-mod-*'. Modules built for the old package can stop nginx from starting.Test the configuration with
nginx -t.Restart nginx with
systemctl restart nginx. A reload keeps the old master process, and the old binary, running.Replace nginx containers: pull the new image, then recreate the container. If your Compose file pins a tag on a branch older than 1.30, such as
nginx:1.28, pulling it again changes nothing. Move the tag to a fixed release.Confirm what is running: the package revision on the host, and
docker exec <container> nginx -vfor containers.
If a step fails, the old nginx keeps serving traffic as long as you have not restarted it. Run nginx -t before every restart, so a broken configuration never takes the site down.
What we found on the servers we run
We checked the servers we maintain in the days after the disclosure. Most had already received the fixed package through Ubuntu's automatic security updates, so our work there was confirming that the running nginx used the new binary.
Two servers would not have been fixed by a plain update:
A repository for the wrong release. One server had nginx's own package repository configured for a newer Ubuntu release than the one installed. Its system nginx was already patched, but a blind
apt upgradewould have replaced it with a build made for another operating system. We turned the repository off.nginx in a container. On another, nginx ran in Docker from an image that had been pulled long before. Host updates never reach it. Pulling the current image and recreating the container moved it to 1.30.7 in a few seconds of downtime.
Neither problem shows up if you only run nginx -v on the host. Both show up in a two-minute check per server, which is why we keep a list of what runs where for every platform we maintain, such as Marafiq, the training platform we built and maintain (case study). We describe that habit in what happens after your software launches.
The same week, PHP shipped its own security release. If your app runs on PHP-FPM behind nginx, check both: PHP's Nov 19 security fix: is your Laravel app affected?
You may not need anyone for this. On managed hosting that patches the web server for you, the fix is a support ticket and a check afterward that the version changed.
Next step
Not sure what runs on your servers, or whether your nginx and PHP are both patched? We can check your setup and tell you what needs to change. Book a short intro call.

