logoComputeSphere
Security releases

nginx November 2026 Security Release: Upgrade to 1.30.7 or 1.31.9

P
By Peter Ekhator
•3 min read•

On November 18, 2026, nginx released 1.30.7 (stable) and 1.31.9 (mainline) with fixes for 10 vulnerabilities. nginx rates three of them major. The most widely relevant is CVE-2026-123007, memory corruption in HTTP/2 flow control, which affects every version from 1.9.5 to 1.31.8. Upgrade to 1.30.7 or 1.31.9.

If you serve a static site or a single-page app from an nginx image, or use nginx as a reverse proxy in front of your app, this applies to you.

What the major bugs do

  • HTTP/2 flow control (CVE-2026-123007): in nginx's words, "a flow control window overflow in HTTP/2 might allow an attacker to cause a segmentation fault in a worker process, or might have potential other impact." A crashed worker drops the connections it was handling. nginx doesn't say more about the "other impact", so treat it as more than a crash.
  • Request bodies over TLS (CVE-2026-118899): "worker processes might get caught in an endless loop while reading the request body over SSL." nginx's advisory names it "Infinite loop while reading client request body over TLS 1.3."
  • Mail proxy (CVE-2026-113425): "use-after-free might occur in a worker process in the mail proxy server." This only matters if you use nginx's mail module.

The release also fixes four medium and three minor issues. They cover HTTP/2 and HTTP/3 use-after-free bugs when worker_connections runs out, the resolver directive, alias with try_files, SNI handling for client certificates in the stream module, and the stream ssl_preread module. One minor fix, for PROXY protocol version 2 (CVE-2026-120993), is only in 1.31.9; 1.30.7 isn't affected by it. The advisory list has every CVE.

Which versions fix it

  • nginx stable: 1.30.7
  • nginx mainline: 1.31.9

For the HTTP/2 bug, every version from 1.9.5 through 1.31.8 is affected, and the other issues have their own ranges on nginx's advisory list. nginx names no other fixed versions, so if you're on an older stable branch, move to 1.30.7.

How to check your app

Find the nginx version inside the image you actually deploy: run nginx -v in the container, or check the tag or digest in your Dockerfile's FROM line. Anything below 1.30.7 on the stable branch, or below 1.31.9 on mainline, misses some of these fixes.

A floating tag such as nginx:stable-alpine only moves to the fixed release once the image is rebuilt from it, so check the version the image really contains.

Updating on ComputeSphere

If you deploy from your own Dockerfile, update the FROM line to a fixed release, for example nginx:1.30.7-alpine or nginx:1.31.9-alpine, and push. With auto-deploy on, the push builds a new image and redeploys your service. If auto-deploy is paused, as it is after a rollback, the push doesn't deploy: choose Resume auto-deploy on the service first, or start a build by hand (deploy actions). With a floating tag, rebuild the service so it pulls the patched image. A running service keeps the image it was built with, so it doesn't pick up the fix until it's rebuilt.

If you deploy a static site or single-page app from source without a Dockerfile, it isn't served by nginx, so these fixes don't apply to it and there's nothing to rebuild.

After the deploy, check the build log for the nginx version and run nginx -v again if you can.

Sources

Last checked November 19, 2026.

Predictable cloud, from your first push.

Fixed price per spherelet, flat plan per team — ship without DevOps or surprise bills.

Start free trial

14-day free trial

Share this article

Ship your next service on ComputeSphere

Predictable per-spherelet pricing, a flat plan per team, and managed primitives built in — no DevOps, no surprise bills.

Deploy your first app in minutes.

Connect a repo or start from a template — live URL, SSL, and zero DevOps, on predictable monthly pricing. 14-day free trial.