Last updated 18 November 2026, 19:00 CET. Remote code execution as the nginx worker is confirmed. nginx 1.30.7 and 1.31.9 are out. Hadrian is fingerprinting nginx and raising Potential risks for the vulnerable ranges.
The short answer
Remote code execution as the nginx worker is confirmed. On 18 November 2026 Xint published the five bugs as nginx2root, and confirmed command execution on each one, with no login. The broad path is CVE-2026-123007, an HTTP/2 flow-control window overflow on any server with HTTP/2 enabled. nginx.org's changelogs for 1.30.7 and 1.31.9 name all five.
The fixed open source builds are 1.30.7 and 1.31.9. NGINX Plus names four of the five in PLS.37.0.8.1 (LTS) and PLS.37.3.0.1 (CR), also dated 18 November 2026. CVE-2026-123633 is named in the previous Plus builds, PLS.37.0.7.1 and PLS.37.2.0.1, from 14 October 2026. F5's score for the two HTTP/2 bugs, on Ubuntu's CVE-2026-123007 page and the CVE-2026-123633 page, is 9.2 on CVSS 4.0 and 8.1 on CVSS 3.1. Debian and Ubuntu have no fixed package yet.
What we know
- Bug: Five separate bugs, each in a worker process. CVE-2026-123007 overflows the HTTP/2 flow-control window. CVE-2026-123633 and CVE-2026-121810 are use-after-free in HTTP/2 and HTTP/3 when worker_connections run low. CVE-2026-123634 is a use-after-free in the resolver when the same name is resolved from subrequests at the same time. CVE-2026-113425 is a use-after-free in the mail proxy.
- Pre-auth: CVE-2026-123007 needs HTTP/2 enabled on a listener an attacker can open. No login. CVE-2026-123633 needs HTTP/2 and a proxy to a backend, with the worker low on worker_connections. Xint's confirmed path for that bug, and for the HTTP/3 bug CVE-2026-121810, has the worker open a TCP connection to the attacker. CVE-2026-123634 needs the resolver to reach the attacker's DNS server. The mail proxy path uses auth_http and fires during login, without valid credentials.
- Ranges: The ranges in the table are the ones nginx.org's advisory prints for each CVE. Xint's tested resolver path starts at 1.13.4, and its tested mail path at 0.5.15. Ubuntu's tracker marks CVE-2026-123633 vulnerable on Ubuntu 16.04 through 26.10, including releases older than 1.19.7, and says a cleartext HTTP/2 listener on those older packages can reach the same bug. Ubuntu 14.04 has no HTTP/2 and is marked not affected for CVE-2026-123007 and CVE-2026-123633.
- Fixed builds: 1.30.7 and 1.31.9 name all five. Plus PLS.37.0.8.1 and PLS.37.3.0.1 name CVE-2026-123007, CVE-2026-121810, CVE-2026-123634, and CVE-2026-113425. Plus PLS.37.0.7.1 and PLS.37.2.0.1 name CVE-2026-123633. The R36 notes stop at R36 P8 on 22 July 2026 and do not name these CVEs. nginx.org's advisory page names each CVE. F5's articles are K000163926 and K000163928 for the two HTTP/2 bugs, and the index is K000164058. Debian marks bookworm 1.22.1-9+deb12u10, trixie 1.26.3-3+deb13u10, and sid 1.30.6-3 vulnerable for CVE-2026-123007, with no fixed version. Ubuntu 16.04 through 26.10 are marked vulnerable for the same CVE, with no fixed package.
- Evidence: Xint confirmed command execution as the nginx worker for each of the five, including an ASLR bypass by leaking addresses. nginx.org records a segmentation fault in the worker for CVE-2026-123007 and CVE-2026-123634. Ubuntu's pages for the two HTTP/2 bugs, linking to F5, state code execution.
- Score: Ubuntu scores CVE-2026-123007 and CVE-2026-123633 at 9.2 on CVSS 4.0 and 8.1 on CVSS 3.1. The 9.2 on this alert is that CVSS 4.0 number. nginx.org rates CVE-2026-123007 and CVE-2026-113425 major, and the other three medium.
What is still unconfirmed
- A kernel fix. Xint confirmed a separate use-after-free in the Linux kernel SCTP send path, present since v4.15, and confirmed that chaining it with CVE-2026-123007 produced root on the host, including from nginx in a container. The write-up of that chain stays withheld until a kernel fix exists.
- Exploitation in the wild. CISA's Known Exploited Vulnerabilities catalog dated 17 November 2026 does not list these CVEs. The nginx.org advisory, the Plus release notes, and Xint's write-up do not report exploitation in the wild.
What Hadrian is doing
- Customers: Hadrian is already on this. We are fingerprinting nginx, including inside container images and products that ship it, and creating Potential risk alerts for the vulnerable ranges. CVE-2026-123007 matches when the Server header reports nginx 1.9.5 through 1.30.6, or 1.31.0 through 1.31.8. CVE-2026-123633 matches 1.19.7 through 1.30.6, or 1.31.0 through 1.31.8. Stable builds from 1.30.7 and mainline builds from 1.31.9 stay off those alerts. Fingerprints already list nginx for the HTTP/3, resolver, and mail bugs.
- Verified: A verified check is in development. The fingerprints and the range alerts are already running.
What to do now
- Find the runtimes. Hadrian is already creating Potential risk alerts where the version banner falls in the vulnerable range. In Hadrian, open Risks and review those findings for CVE-2026-123007 and CVE-2026-123633. Open the Technologies page and search for nginx, including products that embed it. If the version is blank, keep the asset on the list until the owner confirms the build. The HTTP/3, resolver, and mail bugs are on that technology list.
- Get the exact build. For each nginx, record the service, the build, the distribution, whether it is on the internet, and the owner. Include container images and nginx shipped inside another product. Where Hadrian shows nginx without a build, ask the owner for it. Compare the package with the distribution advisory, because a backport keeps the upstream version string.
- Install the fixed build, internet-facing services first. Open source: 1.30.7 or 1.31.9. Plus LTS: PLS.37.0.8.1. Plus CR: PLS.37.3.0.1. On Plus, match PLS.37.0.8.1 or PLS.37.3.0.1. nginx -v on those builds prints the open source base, 1.29.8 or 1.31.8, and the Plus notes name the fixes on top. PLS.37.0.7.1 and PLS.37.2.0.1, from 14 October 2026, name CVE-2026-123633. The other four are named in the 18 November Plus builds. Debian and Ubuntu have no fixed package in their trackers. The R36 release notes do not name these CVEs. The same 1.30.7 and 1.31.9 changelogs also fix CVE-2026-118899, an endless loop while reading a request body over SSL, which nginx.org rates major, plus CVE-2026-125283, CVE-2026-120967, and CVE-2026-123640. CVE-2026-120993 is named in the 1.31.9 changelog and in Plus PLS.37.3.0.1. Restart nginx after the install so the new binary is the one running.
- Rebuild container images. Patching the host leaves the nginx inside an image as it was. Rebuild the image and redeploy it.
While you patch, watch for nginx worker processes dying with a segmentation fault. The HTTP/2 control frames used for CVE-2026-123007 are not written to the access log as requests.
What happens next
Debian and Ubuntu packages that name these CVEs are the next builds to install. Xint is holding the SCTP write-up until a kernel fix exists.
We will update this post with the confirmed affected versions, the fixed builds per vendor, and detection guidance. Hadrian users will receive a follow-up bulletin with the same information and any affected assets in their attack surface.
Keep checking this post for updates.

%401x.png)


