opened image

nginx: five vulnerabilities, one of which is 21 years old. How to update the web server

On October 14, 2026, nginx 1.30.6 and 1.31.7 were released. They fix five vulnerabilities. Three of them can lead to arbitrary code execution on the server. One of the bugs had been present in nginx since 2005.

The vulnerabilities do not affect all servers, only those with certain configurations. Figuring out your configuration takes a long time, while updating takes 5 minutes. So our advice is simple: update nginx. Instructions below.

ZOMRO / contact form

Need help from a system administrator?

Describe the issue and we will get back to you within 15 minutes.

Message us on Telegram

What is nginx

nginx is the front desk receptionist of a hotel. Every website visitor goes to it first. The receptionist decides where to send them: serve a ready-made page, pass the request to PHP or Node.js, or hand over an image.

nginx is installed on a huge number of servers around the world. It is often installed without the owner even knowing: it comes bundled with control panels such as ISPmanager, FastPanel, HestiaCP, and aaPanel. If you have a website on a VPS, it is very likely that nginx sits in front of it.

If something is wrong with the receptionist, the whole hotel suffers.

What happened

Five bugs were found in nginx. Each one is triggered only under a certain configuration. It is like a lock that breaks only if the door is opened with a particular key while the handle is held down.

Vulnerability

What can happen

When it is dangerous

Score

CVE-2026-15176

Crash, arbitrary code execution possible

With a certain combination of directives. The bug is present in all versions since 2005

9.2

CVE-2026-97205

Crash, arbitrary code execution possible

aio is enabled and SSI pages with include virtual are used

9.2

CVE-2026-93479

Crash, arbitrary code execution possible

map uses regular expressions, and their parts are used in root or log_format

9.2

CVE-2026-97629

May skip client certificate verification

Shared TLS session cache without an explicitly set key

8.3

CVE-2026-95101

Extra data may end up in a request to the website

HTTP/3 is enabled

6.9

The first three bugs involve memory handling. Imagine a warehouse where the storekeeper mixes up the shelves and puts a box where another one is already lying. Sometimes he simply drops everything on the floor, and nginx crashes. And sometimes an attacker can slip in their own “box” with code.

The certificate bug is dangerous for those who let users in with a special certificate instead of a password. In some cases, nginx could let a person through without verification.

Who is affected

Almost everyone running nginx older than 1.30.6 or 1.31.7. One of the bugs is present in all versions starting from 0.1.29. That is 2005.

What is important to know:

  • Control panels. ISPmanager, FastPanel, HestiaCP, aaPanel, and others install nginx themselves. It needs to be updated too, even if you never configured it.
  • Docker. If your website runs in a container based on the nginx image, updating the server will not affect the container. The image needs to be rebuilt.
  • Ingress in Kubernetes. If you use ingress-nginx, check that its version is built on the patched nginx.

No attacks through these vulnerabilities have been recorded yet. But the fixes were released two weeks ago, and the details have already been published. Usually attacks do not take long to follow.

Find out your version

nginx -v

The response will look like nginx version: nginx/1.30.4. Safe versions are 1.30.6 and higher on the stable branch or 1.31.7 and higher on the mainline.

If nginx is installed from Ubuntu, Debian, or AlmaLinux packages. Systems often backport the fix into an older version. The number does not change, but the hole is closed. You can check this in the package changelog.

For Ubuntu and Debian:

apt changelog nginx 2>/dev/null | grep -E 'CVE-2026-(15176|97205|93479)'

For AlmaLinux and Rocky Linux:

rpm -q --changelog nginx | grep -E 'CVE-2026-(15176|97205|93479)'

If the command printed lines with CVE numbers, the fix is installed. If the output is empty, go to step 2.

Update nginx

Ubuntu and Debian:

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

AlmaLinux and Rocky Linux:

sudo dnf upgrade nginx

Control panels. Update the system or nginx through the updates section in the panel. The panel may keep its own nginx build, so check the version again after updating.

Docker. Change the version in Dockerfile or docker-compose.yml, for example to nginx:1.30.6, and rebuild:

docker compose build --pull
docker compose up -d

Check and restart

First, make sure there are no errors in the configuration:

sudo nginx -t

If you see syntax is ok and test is successful, restart nginx:

sudo systemctl restart nginx

Specifically restart, not reload. The reload command only re-reads the configuration, while the old program keeps running. It is like handing the receptionist new instructions but leaving the same person behind the desk. Websites will be unavailable for about a second.

After the restart, run nginx -v again and open your websites in a browser.

If you cannot update right now

Sometimes nginx cannot be touched until the weekend. In that case, you can temporarily remove the settings that trigger the vulnerabilities. This is not a substitute for updating, but a bandage until you see the doctor.

First, look at which settings you have:

sudo nginx -T 2>/dev/null | grep -nE '^\s*(aio|ssi|ssl_session_cache|ssl_session_ticket_key|http3|map)\b'

Then, depending on what you found:

Found

What to do temporarily

aio on and ssi on

Disable aio or do not serve SSI pages

map with regular expressions

Use named groups and only inside the block with the match

ssl_session_cache shared without ssl_session_ticket_key

Remove the shared cache or set a key from a file via ssl_session_ticket_key

http3 on

Add proxy_request_buffering off; or temporarily disable HTTP/3

After making changes, run sudo nginx -t and sudo systemctl reload nginx again. Here reload is suitable because only the configuration is changing.

If you are not sure what you are doing, it is better not to touch the configuration and to update nginx at the first opportunity. An incorrect edit can bring down all the websites on the server.

Checklist

  • Found out the nginx version with the nginx -v command
  • Checked the package changelog if the version is old
  • Updated nginx via packages, the panel, or Docker
  • Checked the configuration with nginx -t
  • Restarted nginx using restart, not reload
  • Made sure the version is 1.30.6 or 1.31.7 and higher
  • Checked that all websites open

Don’t want to figure it out yourself?

nginx carries all of the server’s websites. One typo in the configuration, and none of them open. And if nginx is inside a panel or in Docker, it is unclear where exactly to update it.

For such cases, Zomro has two options.

SOD: we will update nginx for you

Our system administrator will:

  • find out where nginx was installed from: packages, a panel, or Docker;
  • update it to a safe version;
  • check the configuration for dangerous combinations of directives;
  • make sure all websites work after the restart.

Price: €12.50 for every 15 minutes of work.

Order an nginx update

Premium: fast help when you need it

If websites do not open after the update, every minute costs money. For a regular technical request, a response can take up to 10 hours. With Premium, we respond within 5 to 30 minutes.

New vulnerabilities appear every week. With Premium, you will not have to deal with them alone.

Get Premium