On this page (7 sections)
Ubuntu published security notice USN-9182-1 on 2026-11-20. It covers three nginx vulnerabilities that were published on 2026-11-18: two can be used to crash or hang nginx, and one can let a remote client slip past stream routing rules.
If you run nginx on Ubuntu, or run NGINX Open Source or NGINX Plus elsewhere, read on. Whether you are affected depends heavily on which directives your configuration uses, so the checks below matter as much as the update.
What was disclosed
The Ubuntu notice bundles three separate issues. The technical descriptions come from the F5 advisories referenced by the GitHub advisory entries; Ubuntu credits individual researchers for two of them.
| CVE | CVSS v4 | Weakness | Impact |
|---|---|---|---|
| CVE-2026-118899 | 8.7 (High) | CWE-835, infinite loop | Remote, unauthenticated denial of service |
| CVE-2026-123640 | 6.9 (Medium) | CWE-1289 | Forged stream variables, routing bypass, possible information exposure |
| CVE-2026-125283 | 6.9 (Medium) | CWE-191 | Worker process crash (segmentation fault) |
Technical details in plain terms
CVE-2026-118899: TLS 1.3 infinite loop
When a listen directive with the ssl parameter is used in the http block with TLSv1.3 enabled, a specially crafted TLS connection can send an nginx worker into an infinite loop while it reads the HTTP request body. The worker then stops accepting new connections and stops processing existing ones, per the GitHub advisory and the F5 advisory. No authentication is needed. The CVSS v4 metrics show network attack vector, low complexity and high availability impact. Your exposure depends on whether you have an SSL listener in the http block with TLSv1.3 enabled.
CVE-2026-123640: stream SSL preread routing bypass
This one affects setups using ngx_stream_ssl_preread_module. A crafted ClientHello from an unauthenticated attacker can forge the values of the module's variables, which influence virtual server selection. According to the GitHub advisory and F5, an attacker may be able to bypass stream routing segmentation and reach a privileged or internal backend that should be unreachable, and potentially gain access to sensitive information. It may also cause a disagreement with a proxied server that terminates TLS without TLS 1.3 support.
CVE-2026-125283: try_files, alias and map
When try_files and alias are used with a map variable, certain combinations of regular expression captures in the map and in try_files can cause a segmentation fault in a worker process, as described in the GitHub advisory and F5 advisory. The worker process terminates unexpectedly.
For all three, F5 states there is no control plane exposure; these are data plane issues only. F5 also notes that software versions that have reached End of Technical Support are not evaluated, so an old unsupported build may be vulnerable without being listed.
Who is realistically exposed
- Any nginx with an SSL listener in the http block and TLS 1.3 enabled (CVE-2026-118899).
- Hosts using the stream module with ssl_preread to route connections to different backends, for example a shared TLS entry point in front of internal services (CVE-2026-123640).
- Sites whose configuration combines alias, try_files and a map variable with regex captures (CVE-2026-125283).
How to check your exposure
Start with the installed version, then look for the risky directives. This command lists the installed nginx package versions on Ubuntu or Debian; compare the result with the version shown on the USN page for your release.
apt list --installed 2>/dev/null | grep -i nginxThis read-only command prints the full effective configuration and searches it for the directives involved. Run it as root; any matching lines tell you which of the three issues could apply to you.
nginx -T 2>/dev/null | grep -nE 'ssl_protocols|listen .*ssl|ssl_preread|try_files|alias|^\s*map 'Interpret the output like this: an ssl listener with TLSv1.3 enabled points to CVE-2026-118899; ssl_preread inside a stream block points to CVE-2026-123640; try_files and alias together with a map variable points to CVE-2026-125283. If none appear, your exposure is lower, but updating is still the right move.
What to do now
- Read USN-9182-1 and note which of the three CVEs are addressed for your Ubuntu release.
- Update the nginx packages with your normal package manager workflow (command below).
- Validate the configuration with nginx -t, then restart nginx as your update process requires.
- Confirm the new package version with the apt command above.
- If you cannot patch immediately, review whether the affected directives are really needed and note the exposure until you can update. This is not a substitute for the update.
- If you route traffic with ssl_preread, make sure internal backends also enforce their own authentication and are not reachable by network path alone.
- Check that nginx builds you run outside the Ubuntu archive (vendor repositories, containers, NGINX Plus) get the corresponding fixes from F5 or their own vendor.
This refreshes the package lists and upgrades only nginx on Ubuntu. Look for the new version in the output.
sudo apt update && sudo apt install --only-upgrade nginxThis checks the configuration syntax and then restarts the service. Expect a line saying the syntax is ok and the test is successful before the restart runs.
sudo nginx -t && sudo systemctl restart nginxDetection and monitoring
The research contains no reports of exploitation and no published indicators of compromise, so there is nothing specific to hunt for. As general good practice, you can watch for symptoms these bugs could produce:
- Worker crashes: a segmentation fault in a worker is the behavior described for CVE-2026-125283. Review the nginx error log for workers exiting unexpectedly (general nginx logging behavior, not a signature from the advisories).
- Hangs: nginx that stops answering while the process is still running can match the infinite loop described for CVE-2026-118899. Uptime checks that request an HTTPS page will notice this quickly.
- Unexpected backend access: for stream routing, review backend logs for connections that arrive through the wrong virtual server.
External uptime and certificate monitoring, such as Webforta Monitor, can alert you when a site stops responding, but it cannot tell you whether this flaw caused an outage. For background on availability checks, see uptime monitoring explained.
Related reading
A web application firewall can add a layer in front of web servers, but it is not a replacement for patching.
Sources
This article is based on the public sources below. Details can change as vendors and researchers publish more; check the original advisories before acting on version numbers.
