Skip to Content (Press Enter)
Is your Statamic site hiding the pain like Harold? Find out

Every site on my maintenance plans gets the NGINX fix this week

NGINX fixed ten vulnerabilities on 18 November 2026. Every site on a Statamic maintenance plan will be running the fixed version this week.

by Stephen Meehan in Maintenance Services, Server Logs, News

Illustration of NGNIX logo being pulled from multiple directions.

On the evening of 18 November 2026, I updated the first client server to the fixed version of NGINX, a few hours after it was released.

NGINX had fixed ten vulnerabilities at once, and two of them are serious enough that I want every server I manage updated this week.

Harold's smile or Will Ferrell's tears? Type your website's address into my free Statamic health check to see how many updates it's missed, whether it still gets security updates and which face it earns.

What is NGINX?

NGINX (pronounced "engine X") is software that runs on the server behind a website. When someone visits, NGINX receives the visit, passes it to the site, and sends the finished page back to their browser.

It's open source, meaning its code is public and free for anyone to use, and around 3 in 10 websites run on it. Apache, its older rival, runs another 2 in 10. Between them they handle about half the websites on the internet, including every site I look after.

Because it sits in front of everything else, a vulnerability in NGINX affects the whole site, whatever runs behind it. WordPress, Laravel and Statamic sites on NGINX all need the same fix. Sites on Apache aren't affected by these vulnerabilities.

What are the NGINX vulnerabilities?

The two most serious are in HTTP/2, the newer and faster way browsers talk to servers. Most modern servers use it, mine included.

In the worst case, someone could send a long run of specially shaped traffic to a website and make its server run their own code, without logging in. One of the two, CVE-2026-123007, affects every version of NGINX released since 2015. CVE stands for Common Vulnerabilities and Exposures, the public list of known security vulnerabilities.

The other, CVE-2026-123633, affects servers that hand each visit on to another program, as every Statamic site does. It works when NGINX is running out of room for new connections, which an attacker can cause.

Security researchers at Wiz confirmed that CVE-2026-123007 works against a server sending out ordinary pages and images, with no extra software installed. A website needs nothing unusual to be exposed.

Both score 9.2 out of 10 on the Common Vulnerability Scoring System (CVSS). The other eight vulnerabilities are less severe, and most are in NGINX features that a typical Statamic site doesn't use. The same update fixes all ten.

Has anyone been attacked?

No attacks had been reported when the fix was released. The researchers who found the most serious vulnerability reported it privately to NGINX, which gave it time to prepare the fix before anything was made public.

That window has closed. On release day, the security company Rapid7 published working code showing how the attack is done. It needs a lot of traffic and the right kind of hardware to succeed, but anyone can now study it.

Once working attack code is public, the time to update is days, not weeks.

What I'm doing for sites on my maintenance plans

This is one of the critical patches that can't wait for the monthly update. Ubuntu, the operating system on my servers, hadn't released its own fixed version on release day. NGINX had, so I'm installing NGINX's fixed release, 1.30.7, rather than waiting.

Sites on the Max plan come first, because Max includes priority response. I started on those on 18 November. Every site on the Core and Plus plans will be done by Friday 20 November.

For each server, I:

  1. Install NGINX 1.30.7 on every production and staging server I look after.

  2. Restart NGINX fully. A lighter reload leaves the old version running in the background.

  3. Confirm every part of NGINX started after the update, so nothing is left on the old version.

  4. Install any other security updates waiting on the server. If one needs a server restart, I do it at a quiet time or arrange it with the client's IT team.

  5. Check that every site and its Control Panel work as before.

You don't need to do anything. I'll let you know when your site is done.

What if your site isn't on a maintenance plan?

Ask whoever looks after your server which version of NGINX it runs. The fixed versions are 1.30.7 and 1.31.9, or anything newer.

If the server uses the NGINX that comes with Ubuntu or Debian, the fix may not be out yet. Until it is, turning off HTTP/2 closes off the two most serious vulnerabilities. Your site still works without it, and pages load slightly slower until it's turned back on.

The NGINX security advisories list every vulnerability and the versions it affects. Canonical's advisory shows when each version of Ubuntu gets its fix.

Keeping server software like NGINX up to date is part of every website maintenance plan I offer. Sites on a plan get fixes like this installed and checked without their owners having to ask.

18th November, 2026 by Stephen Meehan in Maintenance Services, Server Logs, News
.

Get a measurably better website

Your online presence matters, increase engagement, lower bounce rates, and improve conversions.
Design & Build