NGINX 1.31.9 and 1.30.7: CVE-2026-123007 HTTP/2 RCE and four more flaws fixed
F5 patched five NGINX memory-safety bugs on 18 November; the HTTP/2 flaw CVE-2026-123007 dates to 2015 and Wiz says it can give unauthenticated code execution.
· 8 min read
Written by AI from the sources linked below. How we use AI
On this page
F5 shipped NGINX 1.31.9 (mainline) and 1.30.7 (stable) on 18 November 2026, fixing five memory-safety flaws. The most serious, CVE-2026-123007, is an HTTP/2 flow-control bug that Wiz and Xint both say can give an unauthenticated attacker remote code execution on a server with HTTP/2 enabled. It has been in the code since NGINX 1.9.5, released in 2015. No exploitation in the wild has been reported so far, and both research teams have withheld working exploit code, but five groups found the bug independently, according to Wiz.
Key points
- NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable) fix five CVEs: CVE-2026-123007, CVE-2026-123633, CVE-2026-123634, CVE-2026-121810 and CVE-2026-113425 (nginx.org advisories).
- CVE-2026-123007, an HTTP/2 flow-control flaw, affects every official release from 1.9.5 through 1.31.8 and is rated "Major" by nginx.org and Critical (CVSS 4.0 9.2) by Wiz.
- Wiz says it built working remote code execution exploits against official 1.31.7 and 1.31.8 builds and is not publishing them; Wiz reports no in-the-wild exploitation.
- Turning HTTP/2 off (
http2 off;) blocks CVE-2026-123007 and CVE-2026-123633, but not the other three flaws. - Restart NGINX after upgrading: a reload does not replace the running binary (Xint).
What to do
Who is affected. Anyone running NGINX Open Source from 1.9.5 to 1.31.8 with HTTP/2 enabled is exposed to CVE-2026-123007. NGINX Plus is affected from R33 (37.0.0). The other four flaws have narrower conditions, listed below.
Fix. Upgrade to NGINX 1.31.9 (mainline) or 1.30.7 (stable). For NGINX Plus, Wiz lists 37.0.7.1 and 37.2.0.1 for CVE-2026-123633, and 37.0.8.1 and 37.3.0.1 for CVE-2026-123007. Then restart the service; Xint warns that a reload does not replace the running binary.
Distribution packages. Xint notes that distributions can backport fixes without changing the version printed by nginx -v; it cites Ubuntu 22.04 packages as an example. Check your vendor's security tracker for the CVE IDs rather than comparing version strings.
If you cannot upgrade today.
- HTTP/2 (CVE-2026-123007 and CVE-2026-123633): set
http2 off;in affected server blocks (NGINX 1.25.1 or later) or remove thehttp2parameter fromlistendirectives, reload, and confirm old workers have exited (Wiz). - Resolver (CVE-2026-123634): avoid request-time DNS lookups in
proxy_pass; use fixed upstream groups (Xint). - HTTP/3 (CVE-2026-121810): remove QUIC listeners, set
http3 offand clear theAlt-Svcheader (Xint). - Mail proxy (CVE-2026-113425): bind mail proxy listeners to loopback or restrict access with a firewall (Xint).
How to check. Run nginx -V and look for the HTTP/2 module and version, search your configuration for listen ... http2 and http2 on, and compare with the ranges below. Wiz suggests watching for unexpected worker crashes or commands launched by NGINX, and Xint lists auditd execve monitoring for worker processes. Wiz stresses these are general warning signs, not confirmed indicators of these particular bugs.
What happened
On 18 November F5 published a coordinated security release for NGINX with five fixes, and two research teams published write-ups the same day. The nginx.org security advisories page lists all five as fixed in 1.31.9 and 1.30.7:
- CVE-2026-123007: memory corruption in HTTP/2 flow control, vulnerable 1.9.5 to 1.31.8, rated Major (F5 advisory K000163926).
- CVE-2026-123633: use-after-free in HTTP/2, vulnerable 1.19.7 to 1.31.8, rated Medium (K000163928).
- CVE-2026-123634: use-after-free during response processing in the resolver, listed vulnerable from 0.6.18 (K000163925). Xint gives the first affected release as 1.13.4, so the two sources disagree; check the advisory for your version.
- CVE-2026-121810: use-after-free in HTTP/3, vulnerable 1.25.0 to 1.31.8 (K000163927). The advisories page prints this ID as "CVE-CVE-2026-121810", which looks like a typo.
- CVE-2026-113425: use-after-free in the mail proxy module, listed vulnerable from 0.5.33, rated Major (K000163931). Xint gives 0.5.15 as the first affected release.
The two HTTP/2 bugs get the attention. Wiz Research describes CVE-2026-123007 as an integer underflow in the HTTP/2 send_window and CVE-2026-123633 as a use-after-free in HTTP/2 connection handling, and scores both Critical at CVSS 4.0 9.2. nginx.org rates the second one only Medium, a difference worth noting. Wiz argues the bug is more likely to be exploited when NGINX is configured as a proxy and available connection slots run low.
For CVE-2026-123007, Wiz says it confirmed remote code execution with an ASLR bypass on official NGINX 1.31.7 and 1.31.8 builds, using HTTP/2 over TLS on 64-bit systems serving in-memory response data, and that ordinary static files can reach the vulnerable path through standard TLS processing. The attacker needs to send a large number of WINDOW_UPDATE records, so long-lived HTTP/2 connections carrying a lot of data are the signature to hunt for. Wiz says CDNs and WAFs that terminate HTTP/2 may partly mitigate the attack, depending on how they implement it.
Five groups found the same bug independently, according to Wiz: Wiz Research, Ikotas Labs, Metnir, Rapid7 and Xint. Wiz says it found both HTTP/2 flaws with its AI code-scanning harness, Wiz Atlas, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate the impact. Techmeme's summary of a Forbes report says Xint used GPT 6.1 Sol and GPT-6 Luna; we could not open the Forbes piece to confirm that, and Xint's own write-up does not name a model.
Background
NGINX is widely described as the most widely used open-source web server; Wiz puts it at more than 225 million websites. That reach is why a bug in HTTP/2 handling matters: the flaw is in the server, not in the application behind it, so a site with spotless application code can still be exposed.
HTTP/2 flow control lets each side tell the other how much data it may send before waiting for more permission, using a window that grows with WINDOW_UPDATE frames. Per Xint's write-up, CVE-2026-123007 begins when queued DATA is credited back to the connection window twice, pushing the send window past its maximum. An unsigned underflow in the window check then lets further WINDOW_UPDATE frames through, and the window ends up treated as a negative length in a copy. That produces an out-of-bounds write and discloses NGINX image and heap addresses. The attacker then overwrites a cleanup function pointer and runs commands with the privileges of the NGINX worker process.
This is the second serious memory-safety scare in a short time in the server stack. We covered Java4Shell, CVE-2026-114938, and Wiz explicitly compares the NGINX bugs with it and with PHP2Shell. If you need a refresher on reading the severity numbers in these advisories, see our explainer on what a CVSS score means.
The numbers
Xint says that on 10 November Shodan returned 56.7 million hosts for product:nginx. Only 11.94 million of those expose an identifiable version, and 98.9% of that subset falls in the vulnerable range for CVE-2026-123007. Most hosts hide their version, so the true exposure cannot be counted, but the visible sample suggests almost no unpatched installation is outside the range.
The disclosure timeline from the two research teams is tight. Wiz reported the use-after-free to F5 on 21 October and was told another team had already reported it; F5 sent a patch for review on 10 November. Wiz reported the integer underflow on 16 November, and F5 confirmed on 17 November that it matched CVE-2026-123007 and folded it into the 18 November release. Xint's timeline: discovered 11 October, reported to F5 through HackerOne on 16 October, delivered to the NGINX team on 27 October, patch validated on 10 November, release on 18 November.
How it works
Xint's headline, "NGINX2Root", is about chaining. Its write-up says one researcher found CVE-2026-123007 while preparing for ZeroDay Cloud 2026, and that a fully automated Xint scan found the other four NGINX bugs without human guidance. It does not name the AI model used (see the Forbes note above).
After code execution as the NGINX worker, Xint says it combined the bug with a separate Linux kernel use-after-free in the SCTP send path, which it describes as a zero-day with no CVE assigned yet, introduced in Linux 4.15 in 2018. According to Xint, that chain gives a KASLR bypass and arbitrary kernel function calls, which it says yields root, and it also worked from inside a Docker container and reached the host in its tests on AWS, GCP and Azure. Xint has withheld the final exploitation steps and most SCTP details until a kernel patch exists. Whether the SCTP module is reachable depends on the kernel configuration and container restrictions; Xint suggests adding install sctp /bin/false under /etc/modprobe.d/, which does not unload a module that is already loaded or disable SCTP built into a kernel.
What it means
For operators, the practical message is simple: this is an upgrade-and-restart job, not a wait-and-see one. The affected range stretches across a decade of releases, so long-lived distribution packages and container base images are the likeliest places to find old versions. Check images in your registry, not just live hosts.
For defenders without a quick upgrade path, disabling HTTP/2 is a real option but a blunt one: it removes a performance feature, and it only covers two of the five bugs. Do not treat it as a full fix.
For the wider industry, five independent discoveries of the same flaw in a few weeks is a signal that AI-assisted code scanning is finding deep bugs in mature C codebases at scale. Both Wiz and Xint credit AI tooling in their process. That helps defenders when disclosure is coordinated, as it was here, and it shortens the gap in which a lone attacker could find the same bug without telling anyone.
What we don't know yet
- Whether anyone is exploiting CVE-2026-123007 or CVE-2026-123633 in the wild. Wiz reports none; Xint does not say whether others have published exploit code.
- Whether other distributions have backported the fixes, and under which package versions.
- Which AI model Xint used for its automated scan: its write-up does not say, and the Forbes report we could not open reportedly names two.
- Whether the SCTP kernel flaw will receive a CVE and a fix soon, which decides when Xint will publish more.
- The first affected versions for two of the resolver and mail-proxy flaws, where nginx.org and Xint give different numbers.
What to watch next
Watch for NGINX Plus and distribution advisories (Debian, Ubuntu, Red Hat and container base images) that map the fix to package versions; for a kernel patch for the SCTP bug; and for public proof-of-concept code, which research teams have so far kept back. Cloud providers and CDNs that terminate HTTP/2 may also publish their own guidance.
Sources
- nginx.org security advisories (primary)
- Wiz Research: NGINX HTTP/2 RCE vulnerabilities, CVE-2026-123633 and CVE-2026-123007
- Xint: NGINX2Root, remote code execution write-up
- NGINX2Root summary page
- Forbes, 18 November 2026: AI finds major web security flaws (could not be opened by us; cited as the report behind the Techmeme item)
Written by
The official account of the people who run audiotale.net: announcements, conversation starters and the newsroom's drafts. Posts written with AI say so. Every other account here is a real person.
Read next
CVE-2026-119618: Apache httpd 2.4.71 fixes critical mod_http2 RCE flaw
Apache HTTP Server 2.4.55 to 2.4.70 are affected by a critical mod_http2 race condition that can lead to remote code execution; 2.4.71, released 11 November 2026, fixes it.
audiotale.net team6 min read
F5 and NGINX patch five flaws in 1.31.7 and 1.30.6, three with reported critical scores
NGINX 1.31.7 and 1.30.6 fix CVE-2026-15176, CVE-2026-93479 and CVE-2026-97205; each needs a non-default configuration, and F5's ratings and the project's differ.
audiotale.net team6 min read
agent-framework 1.26.1 and 1.26.2 on PyPI steal credentials: what to do
Two malicious releases of Microsoft's agent-framework package ran a credential stealer at Python startup on 17 November before PyPI quarantined them; 1.26.0 is the clean version.
audiotale.net team6 min read