nginx2root: CVE-2026-123007 Gives Remote Code Execution on HTTP/2 Servers Through 1.31.8
Security / news
nginx2root: CVE-2026-123007 Gives Remote Code Execution on HTTP/2 Servers Through 1.31.8
Xint disclosed five nginx bugs and an unpatched SCTP kernel flaw that lifts a worker shell to root; nginx 1.31.9 and 1.30.7 carry the fixes.
An unauthenticated remote attacker can run commands as the nginx worker user on any server that exposes HTTP/2, provided the build falls between 1.9.5 and 1.31.8 (CVE-2026-123007). Xint, the research group that found it, published the flaw on November 18 together with four other nginx bugs and an unpatched Linux kernel flaw that turns a worker shell into root.
The fix is nginx 1.31.9 on the mainline branch or 1.30.7 on stable. The nginx.org security advisories page lists both as not vulnerable, and Xint's nginx2root write-up reports no exploitation in the wild.
Five nginx bugs, five different preconditions
CVE-2026-123007 is an integer overflow in HTTP/2 flow control that leads to out-of-bounds memory writes. Xint says the vulnerable code dates to nginx 1.9.5 and that every official release through 1.31.8 carries it, as did master on November 10. nginx.org titles it "Memory corruption in HTTP/2 flow control" and rates it major.
The other four are use-after-free bugs, and each needs a specific configuration. Disabling HTTP/2 closes only two of the five.
| CVE | Needs | nginx.org rating | Closed by turning off HTTP/2? |
|---|---|---|---|
| CVE-2026-123007 | HTTP/2 listener | major | Yes |
| CVE-2026-123633 | HTTP/2 plus an upstream proxy | medium | Yes |
| CVE-2026-123634 | resolver, request-derived proxy_pass, mirror | medium | No |
| CVE-2026-121810 | HTTP/3 plus an upstream proxy | medium | No |
| CVE-2026-113425 | Mail proxy with auth_http | major | No |
The score gap matters here. Xint rates the whole set critical but publishes no CVSS vectors, and nginx.org's own scale puts three of the five at medium. The rating that applies to you is the one that matches your listeners: a server with no HTTP/2, no HTTP/3 and no mail block is exposed to none of the five.
The kernel half
Xint also describes a use-after-free or double-free in the Linux SCTP send path, introduced in v4.15 in 2018, that races a send against an association moving to another socket. Chained with an nginx bug, it reached root on the host, and the chain also worked from inside a Docker container running nginx. Xint gives no CVE ID for it, and kernel patches were not available when the post went up. Container restrictions and whether SCTP is loaded decide whether the chain is reachable.
Until a kernel fix lands, Xint suggests blocking the SCTP module with a modprobe rule on hosts that do not need it. That does not unload a module already in memory, and it does nothing for a kernel with SCTP built in.
Where the two sources disagree
Xint and nginx.org give different first-affected versions for two of the bugs. Xint lists CVE-2026-123634 from 1.13.4; nginx.org lists 0.6.18. For CVE-2026-113425 Xint says 0.5.15 and nginx.org says 0.5.33. Both ranges end at 1.31.8, so the fixed versions are not in dispute, but anyone running an old branch should trust the vendor's range.
Timeline and what to do
- October 11: Xint discovers the bugs.
- October 16: reported to F5 through HackerOne.
- October 27: reports reach the nginx development team.
- November 10: Xint finishes validating the patch.
- November 18: patch release scheduled.
Upgrade to 1.31.9 or 1.30.7 and restart nginx; a reload leaves old workers running the vulnerable binary. Distribution packages often backport fixes without changing the version string. Xint's example is Ubuntu 22.04, where 1.18.0-6ubuntu14 became 1.18.0-6ubuntu14.22 while nginx -v still printed 1.18.0. Check the full package version against your distributor's advisory.
Xint's Shodan count on November 10 was 11.94 million nginx hosts with an identifiable version, 98.9% of them inside the affected range. The post is explicit that this is an exposure figure, not a count of vulnerable servers. For related reading on how a score can understate a chain, see Check Point's 7.8 flaw chained behind a 9.2 and the OpenJDK score dispute over Java4Shell.
Sources
More in Security
- 01Ruby2Shell (CVE-2026-132825): Ruby Is Fixed, but GitLab, GitHub Enterprise and Chatwoot Are Listed Without a PatchA one-byte heap overflow in Ruby's case conversion carries a 7.4 local score, while the researchers say stock Rails is remotely reachable and will publish a proof of concept Nov. 25.
- 02NPCI Wants Overlay Permissions Restricted on Sideloaded Apps; Google's 2024 India Block List Omits ThemThe reported ask covers accessibility, device admin and display-over-apps. The pilot Google announced on Oct. 3, 2024 named four other permissions.
- 03CVE-2026-99312: A KVM Nested-AMD Bug Scores 8.8, With Fixes Listed for Three Kernel BranchesThe Linux CNA's scoring notes describe a freed page-table root that a guest can aim at; the commit message describes only a stale MMU context.
- 04CISA's Nov. 18 KEV Additions Include Apache Axis 1.x, Which Has No Fix, With a Nov. 21 DeadlineThree of four new entries carry a three-day federal deadline; LiteLLM's advisory names two different patched versions.