First fixed open-source releases.
| Branch | First fixed release | Verify |
|---|---|---|
| Stable | 1.30.7 | nginx.org advisory or package changelog |
| Mainline | 1.31.9 | nginx.org advisory or package changelog |
nginx security advisories · 1.31.9 changelog
NGINX Plus has a separate release scheme. Use F5's product advisory for its applicable fixed build.
Check binary, modules and config.
Run these on the host or inside each container. Compare installed package versions with the distribution's advisory; nginx -v alone cannot prove that a backport is absent or present.
nginx -v 2>&1
nginx -V 2>&1sudo nginx -T 2>&1 | lessnginx -T reads configuration files on disk. If they changed without a reload, running workers may differ. Also inspect container images, appliances, ingress controllers and any direct-to-origin route.
Make the fix live.
- Choose a fixed upstream release or vendor-confirmed package for every affected deployment.
- Deploy the package or new image, then restart NGINX or use a supported live binary upgrade. A configuration reload does not replace the running executable.
- Check the running process, package build, image digest and service health. Close old workers and long-lived connections as your change plan permits.
- Document any temporary protocol restrictions and remove them only when the fixed service is verified.
Test application traffic after changing HTTP/2 or HTTP/3. gRPC and clients that require those protocols can break when they are disabled.
Trust the complete package record.
Backported fixes often leave the nginx/1.x.y banner unchanged. Compare the full OS package revision or vendor appliance release with its security notice. Do not mark an older distribution build vulnerable solely from the upstream version string.