How to protect your nginx server from CVE-2026-93479 and CVE-2026-15176 (heap overflows)

What are CVE-2026-93479 and CVE-2026-15176?

CVE-2026-93479 and CVE-2026-15176 are two heap buffer overflows (CWE-122) in nginx worker processes. nginx.org fixed them on October 14, 2026, in versions 1.30.6 (stable) and 1.31.7 (mainline), together with three other vulnerabilities (CVE-2026-95101, CVE-2026-97629 and CVE-2026-97205).

  • CVE-2026-15176: triggered when a location uses alias together with rewrite and a set or return directive that references $request_filename, or when $request_filename appears in an access log log_format.
  • CVE-2026-93479: triggered when a map uses regex matching and the root directive or an access log format references the regex capture variables before the map's output variable. Under certain conditions it can also happen with a non-cacheable variable in a string expression. It affects the http and stream modules.

F5 rates both CVSS 3.1 8.1 and CVSS 4.0 9.2; nginx.org rates them medium severity and Red Hat rates them Important.

A remote, unauthenticated attacker can send crafted HTTP requests, although according to F5 they also need "conditions beyond their control". The direct effect is a worker crash and restart: a denial of service (DoS). F5 adds that remote code execution (RCE) is also possible on systems with ASLR disabled or when the attacker can bypass it.

As of November 12, 2026, no trusted source reports active exploitation, and neither CVE is in the CISA KEV catalog. Do not confuse them with CVE-2026-42945, an earlier, different nginx flaw that was reported exploited in May 2026.

Are you affected?

In short: both vulnerabilities depend on specific configurations. If your configuration does not combine alias with rewrite and $request_filename, and does not use captures from a regex map in root or in access logs, you are unlikely to be exposed. Still, the non-cacheable-variable case cannot be ruled out by reviewing your configuration. Update anyway; the same update fixes the other three vulnerabilities.

Vulnerable upstream versions according to nginx.org: CVE-2026-15176 affects 0.1.29 through 1.31.6; CVE-2026-93479 affects 1.30.0 through 1.30.5 and 1.31.2 through 1.31.6. If you installed nginx from the nginx.org repositories, you need 1.30.6 or later (stable) or 1.31.7 or later (mainline), which are already published. If you upgraded to 1.30.4 or 1.31.3 for the earlier CVE-2026-42533, you still need this update. NGINX Plus is also affected.

Do not apply those ranges to your distribution's packages. Distributions ship fixes as backports, and Debian, Ubuntu and Red Hat tie CVE-2026-93479 to their backport of the CVE-2026-42533 fix. That is why Debian 12 and 13 and RHEL 9 and 10 are listed as affected even though their version numbers are below 1.30.0. Go by this list:

  • Debian 13: 1.26.3-3+deb13u10 fixes both (DSA-6575-1).
  • Debian 12: no fix yet.
  • Ubuntu 26.04, 24.04 and 22.04 LTS: 1.28.3-2ubuntu1.12, 1.24.0-2ubuntu7.19 and 1.18.0-6ubuntu14.22 fix both (USN-8955-1).
  • RHEL 10 and RHEL 9 (base package): 1.26.3-16.el10_3.1 and 1.20.1-32.el9_9.1 fix CVE-2026-15176; CVE-2026-93479 remains unfixed.
  • RHEL 9 nginx:1.26 and nginx:1.24 modules and RHEL 8 nginx:1.24 module (not affected by CVE-2026-93479): 1.26.3-10.module+el9.9.0+25249+8b47ea83.1, 1.24.0-9.module+el9.9.0+25250+16ab46e3.1 and 1.24.0-3.module+el8.10.0+25265+69171071.6.
  • Rocky Linux 8 (nginx:1.24): fixed (RLSA-2026:98671). Rocky Linux 9 and 10 and AlmaLinux 8, 9 and 10: no advisory published.
  • cPanel (ea-nginx): EasyApache 4 25.91 (1.31.7) or later fixes both.

Status as of November 12, 2026. For other Debian or Ubuntu releases, check your distribution's security tracker (see Sources). The status of DirectAdmin (CustomBuild) and CloudLinux is unknown: if you use them, check that the bundled nginx is 1.30.6 or 1.31.7 or later, or ask the provider.

How to check your server

All of these commands are read-only. Version of the installed nginx binary:

nginx -v

Only compare it with the upstream ranges if you use nginx.org packages or your own build. It does not see nginx inside Docker containers or a second installation under another path.

On Debian and Ubuntu, list the installed nginx packages and compare them with the list above:

dpkg-query -W -f='${db:Status-Abbrev}${Package} ${Version}\n' 'nginx*' | grep '^ii'
apt-cache policy nginx

Run sudo apt-get update first. An installed version that matches the candidate does not mean you are protected: on Debian 12 the candidate is still vulnerable.

On AlmaLinux, Rocky Linux, RHEL and CloudLinux, compare with the list above:

rpm -q nginx

On cPanel, the upstream part of the version must be 1.31.7 or later:

rpm -q ea-nginx

To see whether your effective configuration uses the directives involved:

sudo nginx -T 2>/dev/null | grep -n -E '\$request_filename|^\s*alias\s|^\s*map\s|log_format|^\s*(root|access_log)\s[^;]*\$|\$[0-9]'

Use it only to know where to look: look for alias with rewrite and $request_filename, or captures such as $1 from a regex map used in root or in logs. No matches does not prove you are safe: no filter can detect the non-cacheable-variable case. Do not share the full output of nginx -T: it can contain secrets.

How to mitigate

Option Best for nginx restart? Durable?
A: update nginx Everyone with a fixed version available Yes Yes
B: change the configuration Systems with no published fix Configuration reload Temporary

Option A: update nginx (recommended)

On Debian and Ubuntu, update only nginx and add the other packages that dpkg-query listed (for example nginx-common) to the command; apt-get upgrade would update the whole system. The package scripts may restart nginx or swap the binary in place:

sudo apt-get update && sudo apt-get install --only-upgrade nginx

On AlmaLinux, Rocky Linux, RHEL and CloudLinux (on RHEL 8 and 9 this updates the enabled module stream):

sudo dnf upgrade nginx

If dnf reports nothing to do on AlmaLinux or Rocky Linux 9 and 10, that does not mean you are protected: no fixed package exists there yet. With the nginx.org repositories, the same commands install 1.30.6 (stable) or 1.31.7/1.31.8 (mainline). On cPanel, make sure EasyApache 4 is at release 25.91 or later.

If the process still uses the old binary after the update (you check this under "After mitigating"), restart nginx. A restart briefly drops open connections; a reload (HUP) is not enough, because it only re-reads the configuration:

sudo nginx -t && sudo systemctl restart nginx

On cPanel servers, confirm the name of the nginx service before restarting it.

Option B: change the configuration (temporary workaround)

F5 suggests these measures until you can update:

  • CVE-2026-93479: do not use unnamed captures ($1, $2…) in regex map blocks. Use named captures instead and limit their use to the block where the regex is matched.
  • CVE-2026-15176: avoid alias inside a location and avoid the $request_filename variable.

These changes can alter which files your site serves: test them in staging first and validate with sudo nginx -t. Red Hat warns that, for CVE-2026-15176, they do not meet its criteria for ease of use, wide applicability and stability.

After mitigating

  1. Check which binary the master process uses (adjust the path if your pid directive differs):
    sudo ls -l /proc/$(cat /run/nginx.pid)/exe
    If the output ends in (deleted), the old, vulnerable binary is still running: restart nginx. If /run/nginx.pid.oldbin exists, the old master process from an in-place binary upgrade is still alive and may serve requests.
  2. Repeat the version checks.
  3. If you applied option B, decide whether to keep the changes once updated, and validate them with sudo nginx -t.
  4. If your system has no fix yet, follow your distribution's security tracker (see Sources) and install the patch as soon as it is published.
  5. Optional: look for worker crashes in the error log, including rotated, compressed logs:
    sudo zgrep -E 'worker process [0-9]+ exited on signal' /var/log/nginx/error.log*
    This is only a weak hint: crashes have many causes, no indicators of compromise (IoC) have been published, and finding nothing proves nothing.

Need help?

Open a ticket at soporte.telecu.cloud and reference: CVE-2026-93479, CVE-2026-15176.

Sources

Tags
How to protect your Linux server from CVE-2026-98432 (Linux kernel IPv4 TCP use-after-free)
How to protect your WordPress site from CVE-2026-87902 (unauthenticated file inclusion)