NGINX November 2026 Security Release: Five RCE-Class Fixes in One Drop
F5’s November 18 NGINX advisory bundles HTTP/2, HTTP/3, resolver, and mail-proxy memory bugs — all CVSS 9.2 RCE-class entries share config prerequisites. Patch 1.30.7/1.31.9 and read the qualifier column before you panic.
On November 18, 2026, F5 shipped a consolidated NGINX security release. The official advisory list is the version truth source; news coverage such as The Hacker News and Wiz Research focused on the HTTP/2 story because it hits common configs.
This article is the qualifier sheet: which of the five RCE-class bugs needs which feature flag, how to roll 1.30.7 / 1.31.9, and where distro packages lie. HTTP/2 specifics: 10-year NGINX HTTP/2 flaw guide.
Five RCE-class issues in one release (and what each needs)
F5 rates all five 9.2 (CVSS 4.0). Exploitability is not identical — match your config to the row before you reprioritize the whole sprint.
| CVE | Impact (vendor summary) | Configuration gate |
|---|---|---|
| CVE-2026-123007 | HTTP/2 flow-control memory corruption | HTTP/2 on |
| CVE-2026-123633 | HTTP/2 use-after-free | HTTP/2 reverse proxy, stressed worker_connections |
| CVE-2026-121810 | HTTP/3 use-after-free | HTTP/3 proxy path |
| CVE-2026-123634 | Resolver use-after-free | Variable-built upstream name + SSI or mirror subrequest |
| CVE-2026-113425 | Mail proxy use-after-free | NGINX as mail proxy with auth_http |
Vendor-listed workarounds (via THN’s summary of F5/CIRCL) are narrow:
- 123634: avoid SSI/
mirrorand variable-built proxied hostnames. - 113425: restrict mail listeners to trusted networks.
Turning HTTP/2 off helps 123007 and 123633 only. Turning HTTP/3 off removes the 121810 setup. There is no single config toggle for the whole list — upgrade stays the default answer.
Where to get the fix
| Track | Fixed release | Fetch |
|---|---|---|
| OSS stable | 1.30.7+ | nginx.org download |
| OSS mainline | 1.31.9+ | Same |
| Docker official image | Tags 1.30.7, 1.31.9 | Hub / vendor registry |
| NGINX Plus | 37.0.8.1, 37.3.0.1, etc. | F5 customer bulletin |
After install, restart or binary-upgrade NGINX. Reloading config without replacing the running binary can leave vulnerable workers alive (called out in THN’s fix section).
Distro lag and version banners
nginx -v prints the upstream version string. Ubuntu and Debian security trackers often still show “needs update” days after nginx.org ships tarballs. Vendors backport patches with a package revision bump — your banner may still read 1.18.0 while the package is patched.
Check your distribution’s CVE page for nginx, not only GitHub Dependabot on app repos.
Inventory checklist (where teams miss the binary)
- Kubernetes ingress controller image (not the app Deployment)
- Sidecar proxies next to mesh gateways
- Legacy VMs still on 1.28.x stable branches called out in press
- Plus vs OSS fork — hotfix build numbers differ
On authorized domains, TLS analyzer and SSL checker help confirm ALPN after you disable HTTP/2.
Exploitation status (as reported publicly)
Coordinated disclosure posts did not describe confirmed mass exploitation at release. CISA KEV had not listed the HTTP/2 CVEs in the first days THN reported — treat that as a snapshot, not a relax signal.
Public proof-of-concept material exists in the ecosystem (THN notes GitHub-hosted demos with narrow lab constraints). Patch production edges regardless.
Same lesson as Log4Shell — different layer
Log4Shell taught teams that shared libraries bite everyone. NGINX teaches the same for shared edge binaries: one proxy fronts marketing, APIs, and admin UIs.
After nginx.org versions are live, proof-backed testing on apps you own still belongs in program — attack surface should list the proxy and the pod.
PandaONE does not replace vendor advisories. For application-layer validation on verified scope, see AI VAPT and domain verification.