nginx vulnerability: is your website safe?

Just a month after the PHP2Shell flaw made headlines, another serious security issue affecting millions of websites has been made public. This time it is in nginx, one of the most widely used pieces of web server software in the world.

The flaws, known as NGINX2Root, were disclosed on 18 November 2026. National cyber security agencies across Europe have issued warnings, and millions of servers were still exposed the morning after the fix was released.

If matm hosts your website, it is already protected. Our servers were updated within 24 hours of the vulnerability going public, and there is nothing you need to do.

If your website is hosted somewhere else, read on to find out what the nginx vulnerability is, how to check whether your website is affected and what to do if you have not heard from your hosting provider.

What is nginx?

nginx (pronounced “engine-x”) is software that runs on the server behind many websites.

When someone visits your website, nginx is often the piece of software that receives their request and sends back the right page. It sits underneath WordPress, WooCommerce, Laravel and most other website platforms, quietly doing its job.

It is everywhere. nginx powers around a third of all websites where the server software can be identified. You probably did not choose it – your hosting provider did – which is exactly why so many website owners are unsure whether they are affected.

What is the NGINX2Root vulnerability?

NGINX2Root is the name for five critical security flaws in nginx, each rated 9.2 out of 10 for severity by F5, the company behind nginx.

They were found by security researchers at Xint, and the most serious was also found independently by teams at Wiz, Rapid7, Metnir and Ikotas Labs. You can read the full details on the official NGINX2Root website and in Xint’s technical write-up.

In plain English:

  • An attacker could run commands on the server without logging in. The most serious flaw uses HTTP/2, a feature that most secure (https) websites use to load pages faster.
  • They could then take full control of the server. Researchers showed that combining it with a separate flaw in Linux gives “root” access – complete control – which is where the name comes from.
  • The flaw has been there since 2015. Every version of nginx released in the last decade contains the vulnerable code.

The nginx team released fixed versions, nginx 1.30.7 and 1.31.9, on 18 November 2026.

Like PHP2Shell, these flaws were found with the help of AI tools. The Register describes NGINX2Root as the latest in a run of AI-discovered flaws in the software the internet is built on – and it is unlikely to be the last.

Is this the same as the PHP2Shell vulnerability?

No. They affect different software, but they have one important thing in common.

Last month we wrote about PHP2Shell, a flaw in PHP, the programming language behind WordPress. NGINX2Root is in nginx, the web server software that sits alongside it.

Both live in the “engine room” underneath your website. That means updating WordPress, your plugins or your theme will not fix either of them. The fix has to be applied to the server itself, which is normally your hosting provider’s job.

Why the nginx vulnerability is so serious

  • No login is needed. An attacker does not need a password or any help from someone at your business.
  • Millions of servers are still exposed. On the morning of 19 November, the Censys NGINX2Root tracker counted around 8.8 million nginx servers still running an affected version with HTTP/2 switched on. Fewer than 5% had been fixed since the flaw was made public.
  • Attack code is already public. Rapid7 has published a working proof-of-concept. There are no confirmed attacks yet, but public attack code is usually when attempts begin.
  • One server can mean many websites. Researchers showed the attack could break out of the isolated space a website runs in, which could put other websites on the same server at risk.

There is no need to panic, but this is not an update that should wait.

What could happen if your website is affected?

If an attacker exploits the nginx vulnerability on your server, the consequences could include:

  • Visitors being redirected to scam or harmful websites.
  • Spam pages or adverts appearing on your website and in Google.
  • Customer details, enquiries or login details being stolen.
  • Google or web browsers showing “this site may be hacked” warnings.
  • Online shops, bookings or payment pages being disrupted.
  • Data protection obligations if personal information is compromised.
  • Lost enquiries, lost sales and damage to your reputation.

Is my website affected? How to check

1. Find out who hosts your website

If you are not sure, check your invoices or ask whoever built your website. If matm hosts it, you are already protected.

2. Ask your hosting provider directly

This is the most reliable check. Send your host a short message such as:

“Has the nginx software on the server hosting my website been updated to fix the NGINX2Root vulnerabilities (CVE-2026-123007 and related CVEs)? If so, when?”

Not every host uses nginx – some use alternatives such as Apache or LiteSpeed – but a good host should be able to give you a clear answer quickly.

3. Do not rely on the version number alone

The official fixed versions are nginx 1.30.7 (stable) and 1.31.9 (mainline) or later. However, many hosts install nginx through their operating system, which often applies the fix without changing the version number. Ask your host to confirm the fix rather than going by the number.

4. Using Cloudflare?

If your website runs through Cloudflare’s proxy (the orange cloud in your DNS settings), Cloudflare says it protects your server from these attacks while it is updated – as long as your server cannot be reached directly. It is a useful safety net, not a replacement for the fix.

5. Manage your own server?

If you or your developer manage your own server, update nginx and then restart it – reloading the configuration does not load the fixed version. If you cannot update straight away, turning off HTTP/2 blocks the two most serious flaws. Xint’s write-up has the full technical steps.

Why haven’t I heard from my hosting provider?

Silence does not mean your website is safe.

The fix was released on 18 November, but several of the most common server operating systems did not have updated nginx packages ready on the day. Some hosting platforms also leave server updates to their customers rather than applying them automatically.

In other words, depending on how your website is hosted, the fix may not have been applied yet – and nobody may have told you. If you have not had an update from your host, it is worth asking.

What to do if your host has not fixed it

  • Ask them for a date. For a vulnerability this serious, the answer should be hours, not weeks.
  • Ask about a temporary fix. Turning off HTTP/2 blocks the two most serious flaws. Some large hosts have already done this for all their customers while they update.
  • Consider Cloudflare. Routing your website through Cloudflare’s proxy adds a layer of protection while you wait.
  • Check for warning signs. Look out for unfamiliar admin users, redirects or spam pages. Our guide to 13 warning signs your WordPress website has been hacked explains what to look for.
  • Consider moving to a host that acts quickly. If your host is slow to fix a vulnerability on this scale, or did not tell you about it, it is likely to be the same next time.

How matm can help

Websites we host were protected within 24 hours of NGINX2Root going public. Our hosting provider patched its managed servers, and our team updated the custom nginx servers we run ourselves.

When something serious happens, our clients hear it from us – not from the news. If your website is hosted elsewhere and you are worried, we can help:

  • Move your website to our secure hosting. We handle the migration for you, with minimal disruption to your website and email.
  • Check your website before it moves. We look for signs of compromise first, so a problem is not carried over to a new server.
  • Keep it protected afterwards. We offer monthly security update services for larger websites and Website MOTs for smaller ones, alongside Cloudflare protection and regular backups as part of our web services.

You can see our hosting prices here.

If you are not sure whether your website is protected from the nginx vulnerability, contact matm at [email protected] or call 01952 883 526 and we will check it for you.

Frequently asked questions about the nginx vulnerability

What is NGINX2Root?

NGINX2Root is the name for five critical security flaws in nginx, the web server software behind around a third of websites. The most serious could let an attacker take control of a website’s server without logging in. Fixes were released on 18 November 2026.

Is my WordPress website affected by the nginx vulnerability?

If your WordPress website is hosted on a server running nginx that has not been updated, it could be at risk. Whether you are protected depends on your hosting provider, not on WordPress itself.

Will updating WordPress or my plugins fix it?

No. The flaw is in nginx on the server, not in WordPress. Your hosting provider needs to update nginx.

Is the nginx vulnerability being exploited?

As of 19 November 2026, no attacks have been confirmed. However, working attack code has been published, and attempts usually follow soon after.

Is my website safe if matm hosts it?

Yes. Our servers were updated within 24 hours of the vulnerability being made public, and no action is needed.

Does Cloudflare protect me from NGINX2Root?

If your website is routed through Cloudflare’s proxy and your server cannot be reached directly, Cloudflare says it protects you while your server is updated. Your host should still apply the fix.

How do I know if my website has been hacked?

Common signs include unfamiliar administrator accounts, visitors being redirected elsewhere, spam pages in Google and browser security warnings. See our 13 warning signs guide.