TL;DR: On November 18, 2026, the nginx team released nginx 1.30.7 (stable) and nginx 1.31.9 (mainline) with fixes for 10 security vulnerabilities. Three of them are rated major, and most of them affect versions going back many years. If you run nginx anywhere (a VPS, Kubernetes, a Docker image, a Windows box under someone’s desk), update it today.
There is no separate patch to apply this time. The fix is the new release, so updating means moving to 1.30.7 or 1.31.9 (or a distro package that backports the fixes).
What was fixed
The biggest risks are in HTTP/2, TLS 1.3 request handling and the mail proxy, because those are all reachable by any client that can connect to your server.
| Severity | Issue | Affected versions | CVE |
|---|---|---|---|
| Major | Memory corruption in HTTP/2 flow control | 1.9.5 – 1.31.8 | CVE-2026-123007 |
| Major | Infinite loop while reading the client request body over TLS 1.3 | 1.13.0 – 1.31.8 | CVE-2026-118899 |
| Major | Use-after-free in the mail proxy module | 0.5.33 – 1.31.8 | CVE-2026-113425 |
| Medium | Use-after-free in the resolver | 0.6.18 – 1.31.8 | CVE-2026-123634 |
| Medium | Use-after-free in HTTP/3 | 1.25.0 – 1.31.8 | CVE-2026-121810 |
| Medium | Use-after-free in HTTP/2 | 1.19.7 – 1.31.8 | CVE-2026-123633 |
| Medium | SNI bypass in client certificate validation (stream module) | 1.25.5 – 1.31.8 | CVE-2026-120967 |
| Minor | Buffer overflow when using alias with try_files | 0.9.6 – 1.31.8 | CVE-2026-125283 |
| Minor | Insufficient validation in the stream ssl_preread module | 1.15.2 – 1.31.8 | CVE-2026-123640 |
| Minor | NULL pointer dereference with PROXY protocol v2 | 1.31.4 – 1.31.8 (mainline only) | CVE-2026-120993 |
Fixed in: 1.30.7+ (stable) and 1.31.9+ (mainline). Full details are on the nginx security advisories page.
Am I affected?
Almost certainly, if you haven’t updated since November 18. Check your version:
nginx -v
Anything below 1.30.7 on the stable branch, or below 1.31.9 on mainline, is vulnerable. One exception: if you use your distro’s own nginx package (Ubuntu, Debian, RHEL), the version number may stay old even after the fix is backported. In that case, check your distro’s security tracker for the CVE IDs above.
How to update
Pick the section that matches how nginx was installed. Always run nginx -t before restarting, so a config problem doesn’t take your site down.
Official nginx.org packages on Debian/Ubuntu
sudo apt update sudo apt install --only-upgrade nginx nginx -v # expect 1.30.7 or 1.31.9 sudo nginx -t && sudo systemctl restart nginx
Official nginx.org packages on RHEL / AlmaLinux / Rocky
sudo dnf upgrade nginx nginx -v sudo nginx -t && sudo systemctl restart nginx
Distro packages (Ubuntu or Debian’s own nginx, EPEL)
Run your usual apt upgrade or dnf upgrade and check the distro security tracker for the CVEs. If the fix hasn’t landed yet, switch to the official nginx.org repository.
Docker and Kubernetes
Pin the fixed version in your Dockerfile, rebuild, and redeploy:
FROM nginx:1.30.7
A floating tag like nginx:stable does nothing for containers that are already running. Pull the new image, rebuild anything built on top of it, and roll out new pods or revisions.
Built from source
wget https://nginx.org/download/nginx-1.30.7.tar.gz wget https://nginx.org/download/nginx-1.30.7.tar.gz.asc gpg --verify nginx-1.30.7.tar.gz.asc tar xzf nginx-1.30.7.tar.gz && cd nginx-1.30.7 nginx -V # copy the "configure arguments" ./configure <same arguments> make sudo make upgrade # binary swap without downtime
The signing keys are listed on the nginx PGP keys page.
Windows
Download nginx/Windows-1.30.7 from the download page. Stop nginx, replace nginx.exe (keep your conf/ folder), then start it again.
Can’t update today?
These reduce exposure while you schedule the upgrade. They don’t replace it.
- HTTP/2 and HTTP/3: turn them off on servers that don’t need them (
http2 off;, and removequicfromlistenlines). This covers three of the ten issues, including a major one. - Mail proxy: if you don’t use it, remove the
mail { }block entirely. - Stream module: review any
ssl_prereadand client-certificate setups instream { }blocks. alias+try_files: check locations that combine the two and restructure them withrootwhere you can.
Then update. None of these settings fixes the TLS 1.3 request-body loop.
Bottom line
Ten CVEs, three of them major, and a vulnerable range covering almost every nginx install out there. The update takes five minutes. Do it now, and remember the servers people tend to forget: staging boxes, internal reverse proxies, and old container images.