nginx.org has released nginx 1.30.7, the stable branch, and nginx 1.31.9, the mainline branch, dated 18 November 2026, with fixes for ten vulnerabilities. Two of them are HTTP/2 memory-safety flaws that independent researchers describe as unauthenticated remote code execution: CVE-2026-123007, which nginx.org lists as “Memory corruption in HTTP/2 flow control,” and CVE-2026-123633, listed as “Use-after-free in HTTP/2.”
The severity labels are not all the same, and they should be kept with their sources. nginx.org’s security advisories rate CVE-2026-123007 as “major” and CVE-2026-123633 as “medium.” Wiz, in an 18 November blog, says both “are both rated Critical, with a CVSS 4.0 score of 9.2.” Sophos, in an advisory on a set of NGINX flaws it refers to as “nginx2root,” says “F5 rates each of them CVSS 3.1 8.1 (High) and CVSS 4.0 9.2 (Critical),” and it includes those two HTTP/2 identifiers in the list. Those figures were not published on the public nginx.org advisories page.
The nginx.org notices and the researcher write-ups TSN has reviewed contain no account of attacks in the wild. The two CVEs are also absent from CISA’s Known Exploited Vulnerabilities catalog, version 2026.11.17, released at 17:53:15 GMT on 17 November and rechecked on 18 November. Sophos does, however, say that “Proof-of-concept exploit code for CVE-2026-123007 is publicly available.”
In brief
- nginx 1.30.7 and 1.31.9, dated 18 November 2026, fix ten flaws, including two HTTP/2 bugs. nginx.org rates CVE-2026-123007 “major” and CVE-2026-123633 “medium”; Wiz calls both critical with a CVSS 4.0 score of 9.2.
- Both need HTTP/2 enabled. The upgrade is the fix; Wiz’s interim step is to turn HTTP/2 off and reload. Products that embed NGINX, such as OpenResty and Kubernetes ingress controllers, need their own vendor updates.
- The advisories reviewed here contain no account of in-the-wild exploitation, and neither CVE is on CISA’s KEV list. Sophos says a public proof-of-concept exists for CVE-2026-123007. CIRCL warns that a vulnerable NGINX instance, on its own, is not the same as host-root access.
NGINX HTTP/2 is required, and the two bugs are not identical
nginx.org lists CVE-2026-123007 as affecting versions 1.9.5 through 1.31.8, with 1.30.7 and 1.31.9 as the first releases that are not vulnerable. CVE-2026-123633 is listed as affecting 1.19.7 through 1.31.8, with the same fixed releases. Wiz says both vulnerabilities require HTTP/2 to be enabled. The same post says CVE-2026-123633 “affects reverse-proxy processing when available connection slots run low,” while CVE-2026-123007 “can also affect NGINX serving content directly,” and that Wiz demonstrated code execution “on NGINX serving ordinary static files, without a backend application or third-party modules.”
Wiz published a table of NGINX Plus builds, which it says are fixed at 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and at 37.0.8.1 and 37.3.0.1 for CVE-2026-123007. Those Plus version numbers are Wiz’s, not a table on nginx.org.
Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint independently found the two HTTP/2 flaws, Wiz said. Rapid7, also on 18 November, described CVE-2026-123007 as a critical integer underflow leading to remote code execution and published a short disclosure timeline with F5. Wiz’s summary of the stakes is: “Successful exploitation could let attackers take control of affected NGINX servers, steal sensitive data, tamper with websites, or disrupt services.”
The same 18 November nginx.org releases also fix eight other flaws, including HTTP/3 and resolver bugs. Those are listed on the news item and the advisories page; they are not the two HTTP/2 issues that researchers have treated as code-execution bugs.
This sits in a familiar patching week. TSN has already covered Apache HTTP Server 2.4.71’s fix for a critical HTTP/2 remote-code-execution flaw, OpenJDK and Red Hat’s advice on the Java4Shell bug, and Apache’s warning that Roller CVE-2026-129448 is being actively exploited. The Roller case is a reminder that a vendor can say a flaw is being exploited without a KEV listing; these NGINX advisories, so far, have not made that claim.
The upgrade is the fix; turning HTTP/2 off is a stopgap
Operators should move to nginx 1.30.7 or 1.31.9, or to a distribution or Plus build that contains the fixes, and restart so the new binary is loaded. Wiz’s interim advice, for those who are not ready to upgrade immediately, is to set http2 off; in the affected server blocks on NGINX 1.25.1 or later, and to remove the http2 parameter from any listen directives, then reload NGINX and confirm that old worker processes have exited. HTTP/2 can be turned back on after the upgrade.
Sophos makes a point that matters for a lot of production front doors: “Products that embed NGINX, such as OpenResty and Kubernetes ingress controllers, need their own updates; confirm patch status with those vendors.” Linux distributions may also backport a fix without changing the version string the binary reports, Sophos noted, so a banner check is not, on its own, proof that a host is patched.
CIRCL’s TR-105, also dated 18 November, adds a further limit on how far a successful NGINX exploit should be assumed to go. Xint’s “NGINX2ROOT” work, CIRCL says, covers five NGINX flaws plus a separate Linux SCTP kernel bug, which had no CVE identifier as of 18 November, that can be chained to obtain root privileges on the underlying host. CIRCL’s caveat is plain: “A vulnerable NGINX instance does not by itself imply host-root access.” The same note says ASLR and related hardening should be treated as useful context, not as a substitute for the patch. That kernel issue is a separate bug, not a built-in property of the two HTTP/2 CVEs.
A medium rating still leaves the HTTP/2 door open
nginx.org’s “major” and “medium” labels are the project’s own ranking. They are not a CVSS score, and they are not a finding that CVE-2026-123633 is harmless. Wiz and the other research groups describe both identifiers as unauthenticated remote code execution, and Wiz’s testing of CVE-2026-123007 on a server that was only serving static files is the sharper end of that claim: the bug, on that account, is in the proxy itself, not in an application behind it. Readers should keep those statements attached to the labs that made them, and keep nginx.org’s milder wording attached to nginx.org.
A public proof-of-concept, which Sophos attributes to CVE-2026-123007, changes the practical timetable even when there has been no public account of attacks in the wild and CISA has not added the identifiers to KEV. The catalog is a federal owed-patch list with its own cycle; the 17 November release, which added a Puppet Enterprise bug, did not include these NGINX CVEs. That absence is a fact about the catalog, not a reason to delay 1.30.7 or 1.31.9.
CIRCL’s host-root caveat cuts the other way, and it should not be ignored. Code execution in an NGINX worker is already a serious incident. It is still not, on CIRCL’s account, the same thing as rooting the host. That second step depends on a separate kernel path. Treating “nginx2root” as if every unpatched HTTP/2 server were already a rooted box would overstate what the public advisories have actually shown.
The next facts to watch are vendor updates for OpenResty and ingress controllers, any later CISA KEV listing, and whether a CVE is assigned to the SCTP kernel issue CIRCL describes.
Sources
- nginx.org, news item, 18 November 2026, announcing nginx-1.30.7 stable and nginx-1.31.9 mainline.
- nginx.org, security advisories, including CVE-2026-123007 and CVE-2026-123633.
- Wiz, “Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007,” 18 November 2026.
- CIRCL, TR-105, 18 November 2026.
- Sophos, security advisory sophos-sa-20261118-nginx2root, 18 November 2026.
- Rapid7, “CVE-2026-123007: Critical NGINX HTTP/2 Integer Underflow Leads to RCE (FIXED),” 18 November 2026.
- CISA, Known Exploited Vulnerabilities catalog, version 2026.11.17, released 17 November 2026, 17:53:15 GMT.
Get TSN’s biggest tech stories, explained.
News and insights across AI, tech, crypto and cybersecurity. Every source linked. Unsubscribe anytime.
Get the newsletterRelated stories
The closest recent TSN account of an HTTP/2 remote-code-execution fix is Apache’s 2.4.71 release. The Roller advisory is the contrast for a vendor “actively exploited” claim that these NGINX notices have not made.
- Apache HTTP Server 2.4.71 Fixes a Critical HTTP/2 RCE
- Apache Roller CVE-2026-129448 Is Being Actively Exploited
- OpenJDK and Red Hat Advise Fixes for the Java4Shell Flaw
Follow @tsnmediahub on X for breaking AI news as it happens.
Follow on X


