What the advisory says

NGINX lists ten security issues fixed in the 18 November 2026 releases. They cover HTTP/2, HTTP/3, TLS request handling, resolver, mail proxy, stream, PROXY protocol and specific alias/try_files configurations. Severity ranges from minor to major. Some flaws need a particular module or configuration, while others affect common request-processing paths.

The advisory lists NGINX 1.31.9 and 1.30.7 as not vulnerable across most issues. CVE-2026-120993 has a narrower fixed-version listing of 1.31.9 and affects 1.31.4 through 1.31.8. Distribution builds can backport fixes, so compare the vendor package advisory as well as the upstream version.

Checks for your systems

Inventory all NGINX instances, including ingress controllers, container images, appliances and partner-managed reverse proxies. Record the package source, branch, enabled modules and whether HTTP/2, HTTP/3, stream, mail proxy or resolver features are in use. Do not rely only on the public website server; staging and internal gateways may also be reachable.

Plan the update through the supported package channel, then verify the running binary and configuration after reload or restart. Test key routes, TLS termination, upstream health and client certificate rules. Keep a record of the instance, release, change window and validation result. Use NGINX’s advisory for issue-by-issue version ranges and its change log for technical notes.