On 18 November 2026, the nginx project released nginx 1.30.7 (stable) and nginx 1.31.9 (mainline) with fixes for ten security vulnerabilities. The most serious, CVE-2026-123007, is a memory corruption bug in HTTP/2 flow control that can allow unauthenticated remote code execution. Researchers have already published a working proof-of-concept, so this update should be treated as urgent for any internet-facing nginx server.
If you run nginx with HTTP/2 enabled on a version from 1.9.5 to 1.31.8, update to 1.30.7 or 1.31.9 now. If you can't update today, turn HTTP/2 off on public listeners until you can.
What is CVE-2026-123007?
The flaw was discovered by Rapid7 and disclosed together with F5, the company behind nginx. According to Rapid7, nginx can miscalculate how much response data an HTTP/2 client has allowed it to send. A remote, unauthenticated client can manipulate HTTP/2 flow-control messages so that nginx later copies data with an invalid length, corrupting memory.
The result can be data disclosure, a crashed worker process, or code running with the privileges of the nginx worker. Rapid7 rates it 9.2 (Critical) under CVSS v4.
There are some practical limits. Rapid7's demonstration needed roughly 128 GB of HTTP/2 traffic and a fast network connection. HTTP/2 connections that pass through another proxy first are much harder to exploit. Those limits lower the risk; they do not remove it, and attackers often improve on published techniques.
The full list of fixes
All ten issues below are fixed in nginx 1.30.7 and 1.31.9, according to the nginx security advisories page. The severity is nginx's own rating.
| CVE | Issue | Severity | Vulnerable versions |
|---|---|---|---|
| CVE-2026-123007 | Memory corruption in HTTP/2 flow control | Major | 1.9.5 – 1.31.8 |
| CVE-2026-123633 | Use-after-free in HTTP/2 | Medium | 1.19.7 – 1.31.8 |
| CVE-2026-118899 | Infinite loop reading request body over TLS 1.3 | Major | 1.13.0 – 1.31.8 |
| CVE-2026-113425 | Use-after-free in mail proxy module | Major | 0.5.33 – 1.31.8 |
| CVE-2026-123634 | Use-after-free in resolver | Medium | 0.6.18 – 1.31.8 |
| CVE-2026-121810 | Use-after-free in HTTP/3 | Medium | 1.25.0 – 1.31.8 |
| CVE-2026-120967 | SNI bypass with client certificate validation in stream | Medium | 1.25.5 – 1.31.8 |
| CVE-2026-125283 | Buffer overflow using alias with try_files | Minor | 0.9.6 – 1.31.8 |
| CVE-2026-123640 | Insufficient validation in stream ssl_preread | Minor | 1.15.2 – 1.31.8 |
| CVE-2026-120993 | NULL pointer dereference with PROXY protocol v2 | Minor | 1.31.4 – 1.31.8 |
Security researchers have rated CVE-2026-123633 critical as well, since it can also corrupt memory during HTTP/2 handling. This release follows earlier nginx security updates in October (1.30.6 and 1.31.7), so servers that missed that round have more to fix.
Who is affected?
- Any nginx server with HTTP/2 enabled, which is most HTTPS sites configured in the last decade.
- Linux distribution packages: Ubuntu, Debian, RHEL, AlmaLinux and others ship their own builds. Check your distribution's security advisory for the fixed package version, because it may not be numbered 1.30.7.
- Docker images and appliances that bundle nginx, including many control panels and load-balancer images.
- NGINX Plus customers should follow F5's own advisories for fixed builds.
- Kubernetes ingress controllers built on nginx need updated controller images from their maintainers.
What to do now
1. Find every nginx instance
Check each server with nginx -v, and don't forget containers, staging servers and appliances. Look for http2 in your listen directives or an http2 on; line.
2. Update
Install the fixed package from your distribution or the official nginx.org repository. Then test the configuration with nginx -t and restart nginx (for example systemctl restart nginx). A reload alone does not replace the running binary.
3. If you can't patch today
- Turn off HTTP/2 on public listeners: remove
http2from thelistenlines, or sethttp2 off;. This blocks the two HTTP/2 flaws at the cost of some performance for browsers. - Put a proxy or CDN in front: services such as Amazon CloudFront or an Application Load Balancer terminate the client's HTTP/2 connection themselves, which makes these attacks much harder. Keep patching anyway.
- Disable modules you don't use: if you don't run nginx as a mail proxy, make sure the mail module is not configured.
4. Watch for signs of trouble
Repeated worker process crashes in the error log ("worker process exited on signal"), unusually large HTTP/2 traffic from single clients, or unexpected processes started by the nginx user are worth investigating.
Need a hand?
Patching web servers across many environments without downtime is exactly what our managed cloud team does every day. If you'd like us to check your servers or help roll out the update, get in touch on WhatsApp.
Sources: nginx security advisories, nginx.org release news (18 November 2026), Rapid7 analysis of CVE-2026-123007. Details may change as vendors publish updates; check the official advisories before acting.