On this page (6 sections)
On 5 November 2026 Ubuntu published USN-8955-2, which brings nginx security fixes to Ubuntu 20.04 LTS, 18.04 LTS, 16.04 LTS and 14.04 LTS. The original notice, USN-8955-1, covered Ubuntu 26.10, 26.04 LTS, 24.04 LTS and 22.04 LTS. This follow-up also fixes CVE-2026-42533 on the older releases.
If you run nginx on any of these Ubuntu releases, especially as a public-facing web server or reverse proxy, this notice is for you. Three of the issues are heap buffer overflows rated critical (CVSS 9.2) that can crash nginx workers and, under certain conditions, possibly allow code execution.
What the notice covers
USN-8955-2 is a companion update. The six issues Ubuntu lists across USN-8955-1 and this notice are:
- CVE-2026-15176: configurations using the alias directive together with rewrite rules. A remote attacker could possibly crash nginx or execute arbitrary code.
- CVE-2026-93479: map directives using regex matching under certain circumstances. Same possible impact.
- CVE-2026-42533: map directives using regex matching and capture variables. Newly fixed for the older releases in this notice. Same possible impact.
- CVE-2026-95101: HTTP/3 requests when proxy_request_buffering is enabled, which could allow data injection into proxied requests. Ubuntu says this affected only 26.04 LTS and 26.10.
- CVE-2026-97205: asynchronous file I/O in certain configurations with Server Side Includes pages, with possible crash or code execution.
- CVE-2026-97629: SSL session ticket keys with a shared session cache but no explicit ticket key rotation, which could let an attacker forge client sessions and bypass client certificate verification. Ubuntu says this affected only 24.04 LTS, 26.04 LTS and 26.10.
Because CVE-2026-95101 and CVE-2026-97629 are described as affecting only newer releases, they are not the concern for the 20.04 and older systems this notice targets.
Technical details of the heap overflows
The three critical CVEs share a pattern: a specific configuration makes nginx handle a variable in a way that leads to a heap buffer overflow (CWE-122) in a worker process. The advisories describe the triggers like this:
| CVE | Configuration pattern |
|---|---|
| CVE-2026-42533 | A map directive with regex matching, where a string expression references the map's regex capture variables before the map output variable. Also reachable via a non-cacheable variable in a string expression under certain conditions. |
| CVE-2026-15176 | A location using alias with rewrite and a set or return directive referencing $request_filename. Also reachable when $request_filename is used in an access log format. |
| CVE-2026-93479 | A map directive with regex matching, where the root directive or an access log format references the map's regex capture variables before the map output variable. Also reachable via a non-cacheable variable in a string expression under certain conditions. |
According to the GitHub advisory for CVE-2026-42533, the attacker is unauthenticated and needs only network access, but the attack complexity is rated high because of conditions beyond the attacker's control. The most likely outcome is a worker process crash and restart, which is a denial of service. The descriptions add that code execution is possible on systems with ASLR disabled or where the attacker can bypass ASLR. The issue is in the data plane only; there is no control plane exposure.
Who is realistically exposed
Exposure depends on both version and configuration. A default nginx install with a plain static site probably contains none of the risky patterns. Sites that are more likely to match include those with regex-based map blocks, alias locations combined with rewrite rules, or custom access log formats that use $request_filename. Agencies and hosting administrators who inherit long-lived configs should review them rather than assume they are clean.
Old Ubuntu releases deserve extra attention. The notice lists the fixed packages for these releases as Ubuntu Pro packages, and for 16.04 it names the Legacy Support add-on (the 14.04 entry is truncated in the excerpt we reviewed, so check the notice itself). If a server is not attached to Ubuntu Pro, confirm with the notice and your package manager whether the fixed version is actually offered to you.
How to check your exposure
First, see which nginx package version is installed. This is read-only; compare the output with the fixed versions in the table below.
dpkg -l | grep nginx| Ubuntu release | Fixed version |
|---|---|
| 20.04 LTS (focal) | 1.18.0-0ubuntu1.7+esm4 |
| 18.04 LTS (bionic) | 1.14.0-0ubuntu1.11+esm5 |
| 16.04 LTS (xenial) | 1.10.3-0ubuntu0.16.04.5+esm10 |
| 14.04 LTS (trusty) | 1.4.6-1ubuntu3.9+esm9 |
Next, search your configuration for the patterns above. This read-only grep lists lines using map, alias, rewrite, $request_filename or log_format across the nginx configuration tree. Review any hits against the descriptions in the previous section.
grep -rnE 'map |alias |rewrite |\$request_filename|log_format' /etc/nginx/Finally, dump the full effective configuration to see included files in one place. This only prints the configuration and tests it; it does not restart nginx.
nginx -TWhat to do now
- Identify every server running nginx, including reverse proxies and containers built on Ubuntu images.
- Check the Ubuntu release and installed nginx packages against the fixed versions above.
- Check whether Ubuntu Pro is attached on 20.04, 18.04, 16.04 and 14.04 systems (Legacy Support add-on is named for 16.04), since the notice lists the fixes as Ubuntu Pro packages.
- Apply the package update and restart nginx.
- Review configs for regex map blocks, alias with rewrite, and $request_filename usage, and simplify where you can.
- Plan an upgrade away from releases that depend on extended or legacy support.
Ubuntu states that a standard system update makes the necessary changes. This refreshes the package lists and upgrades all installed packages, including whichever nginx packages (nginx, nginx-core, nginx-extras, nginx-full or nginx-light) you have. Afterwards, the fixed version should appear when you re-run the dpkg query.
apt update && apt upgradeThis validates the configuration and, only if it passes, restarts nginx so the new binary is loaded:
nginx -t && systemctl restart nginxThen re-run the dpkg query to confirm the version now matches the fixed release. If you installed nginx from upstream packages or built it from source rather than from Ubuntu, this notice does not update it; consult the F5 advisories linked above for fixed upstream versions.
Detection and monitoring afterwards
The advisories say the overflow may cause the nginx worker process to restart, so unexpected worker restarts and bursts of failed requests are worth watching for. The exact log wording is not given in the research, so treat the search below as a general starting point. It looks for worker processes that exited on a signal in the default Debian/Ubuntu error log path. These signs are not proof of exploitation, since the research reports no known exploitation, but repeated crashes deserve investigation.
grep -i 'exited on signal' /var/log/nginx/error.logUptime monitoring helps you notice crash loops quickly; see uptime monitoring explained and Webforta Monitor for availability and certificate checks. For a broader view of your public exposure, a read-only scan of your verified sites can complement patching, though it cannot tell you whether a specific internal configuration is vulnerable.
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.
