Security alerts · November 18, 2026

NGINX: five flaws in HTTP/2, HTTP/3, proxy and mail proxy could allow remote code execution

On November 18, 2026, F5 fixed five NGINX flaws rated CVSS 8.1. An unauthenticated attacker could crash an NGINX worker process over the network and, under certain conditions, run their own code on the server. No exploitation in the wild has been reported yet. Update to 1.31.9 or 1.30.7.

What happened

F5, the company behind the NGINX web server, published an advisory on November 18, 2026 covering five security flaws in the free NGINX Open Source and the commercial NGINX Plus. The EU’s CERT-EU team flagged them the same day. NGINX is one of the most widely used web servers in the world, so this affects a huge number of websites and applications.

The flaws are tracked as CVE-2026-123007, CVE-2026-123633, CVE-2026-121810, CVE-2026-123634 and CVE-2026-113425. They involve HTTP/2 and HTTP/3 handling, forwarding requests to other servers (proxying) with NGINX’s own DNS resolver, and the mail proxy. According to CERT-EU, all of them can let an attacker who is not logged in run their own code on the server with the privileges of the NGINX worker process.

CERT-EU says researchers successfully demonstrated exploitation of CVE-2026-123007, but no attacks in the wild have been reported so far. None of the flaws is in the CISA KEV catalog, and ENISA’s European vulnerability database EUVD records no exploitation either. Still, since a working research demonstration exists, do not put off the update.

Why it is dangerous

Four of the five flaws are use-after-free bugs. A program frees a piece of memory but still holds a reference to it somewhere and later uses it again. Think of a hotel that gives a room to a new guest while the previous guest still has a working key card.

CVE-2026-123007 is a different kind of bug: a number overflow in HTTP/2 flow control. A counter goes past its allowed limit and the program then writes data outside the memory set aside for it. According to F5, this usually ends with the NGINX worker process crashing.

The attack works over the network and needs no login and no action by a user. According to F5, an attacker can crash an NGINX worker process or corrupt its memory, which disrupts the website. They can run their own code if ASLR (memory layout randomization) is disabled or if they manage to bypass it. That code would run with the privileges of the NGINX worker process, which normally does not have administrator rights. F5 adds that only traffic processing is affected, not the management interface.

All flaws are rated CVSS 8.1 out of 10, which means high severity. CVSS is an international severity scale, and this score was assigned by F5 as the vendor and adopted by NVD. It falls short of critical because the attack is rated as complex and depends on configuration. The flaws are not in the CISA KEV catalog, a list kept by the US agency CISA of vulnerabilities that attackers are known to exploit.

Who is affected

Affected are NGINX Open Source mainline up to version 1.31.8 and the stable 1.30.x branch including 1.30.6. According to nginx.org, the lower bound differs by flaw: 1.9.5 for CVE-2026-123007, 1.19.7 for CVE-2026-123633, 1.25.0 for CVE-2026-121810, 0.6.18 for CVE-2026-123634 and 0.5.33 for CVE-2026-113425. For NGINX Plus, CERT-EU lists versions 37.0.0 to 37.0.7.1, 37.1.0 to 37.2.0.1 and releases R34, R35 and R36. F5 did not evaluate versions past End of Technical Support, so do not assume they are safe.

Your risk also depends on configuration. CERT-EU lists these conditions:

  • CVE-2026-123007: HTTP/2 enabled on any listening port, which is common for HTTPS sites
  • CVE-2026-123633: HTTP/2 plus forwarding requests to a backend (proxy), and according to F5 the worker process must also be running low on worker_connections
  • CVE-2026-121810: HTTP/3 enabled plus forwarding to a backend
  • CVE-2026-123634: a resolver set, a proxy_pass target built from request data, and mirror with mirror_request_body off (F5 says SSI can take the place of mirror)
  • CVE-2026-113425: mail proxy with proxy on and auth_http

NGINX typically runs on web hosting, company websites and online shops, as a reverse proxy in front of applications, as a load balancer or in containers. It is also built into other products. For those, ask the supplier.

How to check if you are affected

You can find the version on the server with this command, which only prints information and changes nothing:

nginx -v

For NGINX Plus, the output also shows the Plus release. If NGINX runs in a container, run the command inside it:

docker exec <container-name> nginx -v

If you installed NGINX from your distribution’s packages, also check the package version. Distributions sometimes ship a fix without changing the main version number, so compare it with your distribution’s security notice.

dpkg -l nginx     # Debian, Ubuntu
rpm -q nginx      # RHEL, Rocky, Alma

To see whether you use the features listed above, look at the configuration dump. The nginx -T command only reads and prints it:

sudo nginx -T 2>/dev/null | grep -nE "http2|http3|quic|proxy_pass|resolver|mirror|ssi on|auth_http"

If your site is on shared web hosting, ask your provider which NGINX version they run.

How to fix it

The fix is in NGINX Open Source 1.31.9 (mainline) and 1.30.7 (stable). F5 lists the fixed NGINX Plus versions in advisory K000164058. According to nginx.org, the same releases also fix other bugs, such as an infinite loop with TLS 1.3 (CVE-2026-118899), so updating makes sense even if you do not use the features above. CERT-EU recommends updating as soon as possible, starting with internet-facing systems.

  • List every place NGINX runs: servers, VMs, containers and appliances from suppliers.
  • Start with internet-facing servers, then move on to internal ones.
  • Install the fixed version from the nginx.org repository, from your distribution’s security update or from a new container image.
  • Test the configuration, restart the service and confirm the version. A plain “reload” is not enough, because the master process would keep running the old binary.
  • For containers, pull the new image and recreate the container.
sudo apt update && sudo apt install --only-upgrade nginx
sudo nginx -t
sudo systemctl restart nginx
nginx -v

If you cannot update right away, CERT-EU lists disabling HTTP/2 on externally exposed ports as a temporary measure. Remove the http2 parameter from your listen directives or set:

http2 off;

This only protects against CVE-2026-123007 and CVE-2026-123633, not the other three flaws. Browsers will then connect over HTTP/1.1, so the site keeps working but may be a little slower. It does not replace the update.

What if you may already be compromised

CERT-EU recommends watching for crashes of NGINX worker processes. They show up in the error log as worker process … exited on signal. You can search for them like this (read-only):

sudo zgrep -n "exited on signal" /var/log/nginx/error.log*

If NGINX runs in a container, the error log usually goes to the container output instead. Check it like this:

docker logs <container-name> 2>&1 | grep "exited on signal"

According to CERT-EU, a crash is not reliable proof of a successful attack but rather a sign that someone tried. So also review process creation logs, for example from auditd or your EDR. Look in particular for:

  • processes started by the NGINX user (www-data or nginx), such as a shell, curl or wget
  • new or modified files in web directories and in /tmp
  • unknown cron jobs, new user accounts and SSH keys
  • unusual outbound connections from the server

If you find crashes together with suspicious processes or files, disconnect the server from the network, back up the logs and bring in an incident response specialist. Do not reinstall the server before the evidence has been preserved.

Sources

Articles are put together by an AI agent from public sources (vendors, CISA, ENISA, NVD, SK-CERT, NÚKIB), and version numbers and CVEs are checked against them automatically. Always confirm the steps in the vendor advisory before touching production.

← All alerts · RSS

Need help patching or checking your systems?

I can help you find out which systems are affected, update them safely and check whether an attacker already got in. Let us start with an initial consultation, which is deducted from the project price if we work together.