> ## Content Index
> Fetch the complete content index at: https://claudefox.com/llms.txt
> Use this file to discover other available public pages before exploring further.

# nginx 1.30.7 and 1.31.9 fix two HTTP/2 remote code execution bugs found with AI: what to patch first
- URL: https://claudefox.com/nginx-1-30-7-http2-rce-cve-2026-123633-123007/
- Published: 2026-11-19T03:43:11.000Z
- Updated: 2026-11-19T03:44:27.000Z
- Description: nginx 1.30.7 and 1.31.9 fix ten CVEs, including two HTTP/2 bugs that Wiz says allow unauthenticated remote code execution: CVE-2026-123007 (since 1.9.5) and CVE-2026-123633 (since 1.19.7). How to check your servers, the workaround, and why AI keeps finding these bugs.
- Author: hupicake
- Tags: News

nginx 1.30.7 (stable) and 1.31.9 (mainline) shipped on November 18, 2026 with fixes for ten CVEs. Two of them are in the HTTP/2 code and, according to Wiz Research, let an unauthenticated attacker run code on the server: CVE-2026-123007, a flow-control integer underflow that goes back to nginx 1.9.5 from 2015, and CVE-2026-123633, a use-after-free present since 1.19.7\. Both need HTTP/2 to be enabled. Every nginx version from 1.9.5 through 1.31.8 is affected by at least one of the pair, so if you run nginx with HTTP/2, the answer is to upgrade.

The disclosure is also another data point in a pattern that matters to anyone shipping code with AI help: Wiz found both bugs with its AI code-scanning harness, five research teams reported the same flaws independently, and the nginx changelog credits two outside research groups, Xint.io and Vexera AI, for five of the ten fixes.

## Quick facts

- Fixed releases: nginx 1.30.7 stable and 1.31.9 mainline (nginx OSS). For NGINX Plus, Wiz's table 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.
- CVE-2026-123007: HTTP/2 send\_window integer underflow. Vulnerable 1.9.5 to 1.31.8\. nginx.org severity: major.
- CVE-2026-123633: HTTP/2 connection use-after-free. Vulnerable 1.19.7 to 1.31.8\. nginx.org severity: medium.
- Wiz rates both Critical, CVSS 4.0 score 9.2, and says it confirmed remote code execution with an ASLR bypass. It is not publishing its exploits for now.
- Precondition for both: HTTP/2 enabled. CVE-2026-123007 was shown working against a server serving ordinary static files with no backend application or third-party module, tested over HTTPS on 64-bit systems; CVE-2026-123633 hits reverse-proxy setups when free connection slots run low.
- Workaround if you cannot upgrade yet: turn HTTP/2 off (details below).

## Which of the ten CVEs matter most

The nginx security advisories page lists ten issues fixed in this release. Sorted by the severity nginx itself assigns:

- Major: CVE-2026-123007 (HTTP/2 flow-control memory corruption), CVE-2026-118899 (endless loop reading a request body over TLS 1.3, versions 1.13.0 to 1.31.8), CVE-2026-113425 (use-after-free in the mail proxy module).
- Medium: CVE-2026-123633 (HTTP/2 use-after-free), CVE-2026-121810 (HTTP/3 use-after-free, 1.25.0 to 1.31.8), CVE-2026-123634 (resolver use-after-free, back to 0.6.18), CVE-2026-120967 (SNI bypass in stream client-certificate validation).
- Minor: CVE-2026-120993 (PROXY protocol v2 NULL dereference, mainline 1.31.4 to 1.31.8 only), CVE-2026-125283 (buffer overflow with alias plus try\_files), CVE-2026-123640 (ssl\_preread ClientHello parsing).

Note the gap on CVE-2026-123633: nginx.org calls it medium, while Wiz scores it 9.2 and says it leads to code execution. nginx's own changelog describes it more narrowly, as a use-after-free that might occur in a worker process when using HTTP/2 if worker\_connections were not enough. That condition is the same one Wiz describes: the bug fires when nginx runs short of connection slots and starts closing connections it wrongly treats as idle. Whichever rating you trust, the fix is the same release.

## How the two HTTP/2 bugs work

CVE-2026-123633: nginx keeps a list of idle connections it may close when it needs room. Wiz sends half of an HTTP/2 HEADERS frame so the connection goes on that list, then sends the rest. A request stream now exists, but the connection is never taken off the list. When nginx opens an upstream connection and slots are scarce, it can pick this connection to close, fail to build a GOAWAY frame, free the memory, and then carry on processing the original request with freed memory.

CVE-2026-123007: when a stream with queued data is cancelled, nginx refunds the unsent bytes to the connection's send window without checking HTTP/2's maximum. A later bounds check subtracts that oversized value using unsigned arithmetic, wraps around and stops working. Further down, the value turns negative as a signed length, and the TLS send path does an out-of-bounds memory copy. Wiz says the attacker has to send a large number of WINDOW\_UPDATE frames, which gives defenders something to look for: long-lived HTTP/2 connections pushing unusual amounts of data.

## What to do now

First, find out which version you run and whether HTTP/2 is on. nginx -v prints the version; nginx -T tests the configuration and dumps it, so you can search the output for http2.

```
nginx -v
nginx -T | grep -nE 'http2( |;)|listen.*http2'
```

Anything from 1.9.5 to 1.31.8 with HTTP/2 enabled is exposed to at least one of the two bugs. Upgrade to 1.30.7 or 1.31.9 (or your distribution's patched package). If you cannot upgrade immediately, Wiz's advice is to disable HTTP/2: on nginx 1.25.1 and later set http2 off; in the affected server blocks, and remove the http2 parameter from any listen directives. Then reload nginx, confirm the old worker processes have exited, and turn HTTP/2 back on after upgrading.

```
server {
    listen 443 ssl;      # was: listen 443 ssl http2;
    http2 off;           # nginx 1.25.1+
    ...
}
```

A CDN or WAF that terminates HTTP/2 in front of nginx may block parts of the attack, Wiz says, but that depends on the implementation, so it is not a reason to skip the upgrade. Wiz also suggests watching for unexpected worker crashes and commands launched by nginx, while noting these are general warning signs, not confirmed indicators.

## The AI angle

Wiz says its researchers used Wiz Atlas, the harness behind its AI code-scanning product, to discover both bugs, and used Gemini 4 Carbon and ChatGPT 5.6 Sol to validate that each could give an unauthenticated attacker code execution. Ikotas Labs, Metnir, Rapid7 and Xint found the same flaws independently.

The nginx 1.30.7 changelog makes the shift visible. Xint.io is thanked for four fixes (CVE-2026-123007, CVE-2026-121810, CVE-2026-123634, and CVE-2026-113425 together with Maxim Dounin), and CVE-2026-123633 is credited to Albert of Vexera AI, not to Wiz. Wiz's own timeline says F5 told it on October 21 that another team had already reported that bug. Our observation: half the credits went to outside research groups, for code some of which dates back more than a decade. Wiz's broader argument is that complexity can no longer be relied on as a barrier to discovery, and it points to Java4Shell, another long-hidden memory-safety flaw that Calif disclosed the day before.

For teams, the practical takeaway is about time. If several independent groups with AI tools can find the same memory bug within weeks, the gap between a patch and a working exploit is likely to shrink. Treat nginx and other edge-server releases with security fixes as same-week upgrades, not quarterly ones.

**Try it with your AI.** Paste this into a coding agent that has shell access to the server, to check your nginx exposure without changing anything until you approve.

```
Check whether this server is affected by the nginx HTTP/2 vulnerabilities
CVE-2026-123007 and CVE-2026-123633 (fixed in nginx 1.30.7 stable and 1.31.9 mainline).
Do not change any files yet.
1. Run nginx -v and report the version.
2. Run nginx -T and list every place that enables HTTP/2: an http2 parameter on a listen
   directive, or http2 on; in an http or server block. Report file and line.
3. Tell me whether the version is in the affected range (1.9.5 to 1.31.8) and whether
   HTTP/2 is on.
4. If it is affected, tell me how nginx was installed here (distribution package,
   official nginx.org repository, or built from source) and propose the upgrade command
   for [my distribution]. Show it to me and wait for my confirmation before running it.
5. If I say I cannot upgrade today, propose the exact edit that removes http2 from the
   listen directives and, only if the version is 1.25.1 or newer, sets http2 off; where
   HTTP/2 was turned on (older versions do not have the http2 directive). Show the diff,
   wait for my confirmation, run nginx -t before any reload, and after the reload
   confirm the old worker processes have exited.
Do not touch TLS keys, certificates or credential files, and do not delete anything.
```

## FAQ

Is nginx without HTTP/2 affected? Not by these two CVEs; both require HTTP/2 to be enabled. The same release fixes eight other issues, including CVE-2026-118899 (TLS 1.3 request body loop) and CVE-2026-113425 (mail proxy), so upgrading is still advised.

Which nginx version fixes CVE-2026-123633 and CVE-2026-123007? nginx 1.30.7 stable and 1.31.9 mainline, both released November 18, 2026\. 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.

Is there a public exploit? Not from Wiz, which says it is holding back its proof-of-concept exploits. We found no source reporting exploitation in the wild as of November 19.

Does a CDN in front of nginx protect me? Possibly in part: Wiz says CDNs and WAFs that terminate HTTP/2 may stop the exact payload from reaching nginx, depending on the implementation. Patch anyway.

## Related on claudefox

- [Gemini 4 Carbon is available to paying API developers, with launch pricing that doubles after November 30](https://claudefox.com/gemini-4-carbon-available-api-pricing/)
- [Gemini 4 Hydrogen costs $1.50/$7.50, and it only gets much cheaper than Carbon on December 1](https://claudefox.com/gemini-4-hydrogen-pricing-and-orchestrator/)
- [GPT-6.2 Astra and Sol in the API: prices, the Ultrafast change in March, and what to fix before you switch](https://claudefox.com/gpt-6-2-astra-sol-api-pricing-migration/)
- [Gemini 4 Carbon vs Claude Opus 5.5 and Fable 5.2: benchmarks and pricing compared](https://claudefox.com/gemini-4-carbon-vs-claude-opus-5-5-fable-5-2/)

Source: [Wiz Research: Unauthenticated remote code execution in NGINX](https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities?ref=claudefox.com), [nginx security advisories](https://nginx.org/en/security%5Fadvisories.html?ref=claudefox.com), [nginx 1.30 changelog](https://nginx.org/en/CHANGES-1.30?ref=claudefox.com), [nginx news: 1.30.7 and 1.31.9 released](https://nginx.org/?ref=claudefox.com), [nginx docs: ngx\_http\_v2\_module](https://nginx.org/en/docs/http/ngx%5Fhttp%5Fv2%5Fmodule.html?ref=claudefox.com), [nginx docs: command-line parameters](https://nginx.org/en/docs/switches.html?ref=claudefox.com)

This story first appeared in the [claudefox daily briefing for November 19, 2026](https://claudefox.com/daily-2026-11-19/).