Critical nginx HTTP/2 Vulnerabilities: What They Mean for Your Website

Two critical security flaws have been found in nginx, the web server software behind a large share of the internet. Here’s what they are, who is affected, and what website owners need to do.
If you’ve seen security news this week, you may have spotted warnings about critical flaws in nginx. It’s not a name most website owners have heard of, but it’s one of the most widely used pieces of software on the internet, so the headlines have been loud.
The first question for any business owner is simple: does this affect my website?
The honest answer is "it depends on how your website is hosted". In this post we’ll explain what nginx is, what has been found, who needs to act, and what we’re doing about it at O’Brien Media.
How to read this post Sections marked General advice apply to every website owner, wherever your website is hosted. Sections marked O’Brien Media customers describe what we’ve done, and only apply if we host your website. Sections marked IT teams are technical details for people who run their own servers.
The short version
General advice and facts
- What happened: Two serious flaws were found in the part of nginx that handles HTTP/2, the modern way browsers and web servers talk to each other. Security firm Wiz rates both 9.2 out of 10 for severity.
- How bad could it get? In the worst case, an attacker with no login and no access to your site could run their own commands on the server (the technical term is "remote code execution").
- Is there a fix? Yes. nginx released fixed versions 1.30.7 and 1.31.9 on 18th November 2026.
- Are attacks happening? As of 18th November, there were no reports of the flaws being used in real attacks. One of the research teams, Wiz, says it has working exploits but is not publishing them.
- Is there a workaround? Yes. Turning HTTP/2 off closes both holes until a proper update can be installed.
O’Brien Media customers
- Is my website hosted by O’Brien Media affected? Our web servers do use nginx, so they are in scope. As a precaution, HTTP/2 has been temporarily switched off, which closes both holes. You don’t need to do anything. More detail is in the section for O’Brien Media customers below.
What is nginx?
nginx (pronounced "engine-x") is web server software. When someone types your address into their browser, a web server is the program that receives the request and sends back the page. nginx is one of the two most popular choices for this job, and many hosting companies use it, either on its own or sitting in front of another program, such as WordPress, to speed things up and handle traffic.
What is a web server? A web server is a computer, and the software running on it, that stores your website and delivers it to visitors. Think of it as a shop assistant: a visitor asks for a page, and the web server fetches it and hands it over. nginx is one brand of "shop assistant".
What is HTTP/2? HTTP is the language browsers and websites use to talk to each other. HTTP/2 is a newer version that lets a browser ask for lots of things (images, scripts, styles) at once down a single connection, which makes pages load faster. Most modern websites use it, and visitors never notice it happening.
What has been found?
Two separate flaws, both in nginx’s HTTP/2 code:
- CVE-2026-123007: a memory-corruption flaw in how nginx manages the flow of data. In short, nginx can lose count of how much data it is allowed to send. According to the researchers, this can be reached even on a simple server that only serves ordinary pages over HTTPS. It affects nginx versions 1.9.5 to 1.31.8.
- CVE-2026-123633: a "use-after-free" flaw. Here nginx carries on using a piece of memory after it has already been given back to the system. It mainly matters on servers where nginx passes requests on to another application behind it (a "reverse proxy" set-up), and affects nginx versions 1.19.7 to 1.31.8.
What is a CVE number? "CVE" stands for Common Vulnerabilities and Exposures. It’s a reference number, like a crime reference number, that gives every publicly known security flaw a unique label so everyone is talking about the same thing.
What do "memory corruption" and "use-after-free" mean? Imagine a clerk filing paperwork in numbered boxes. In a memory-corruption flaw, the clerk can be tricked into writing past the last box and scribbling on someone else’s paperwork. In a use-after-free flaw, the clerk throws a file away but then carries on using it, by which time someone else may have put something different in its place. In computers, both mistakes can crash the software, and in the hands of a skilled attacker they can be used to run the attacker’s own commands.
Both flaws need HTTP/2 to be switched on. Without it, neither can be reached.
How serious is it?
Serious, so worth acting on promptly, but not a reason to panic.
- The severity scores are high. Security flaws are scored out of 10. Wiz, one of the research teams involved, rates both flaws 9.2, in the "critical" range. The nginx project’s own listing grades them a little lower, so the exact label varies, but nobody is treating them lightly.
- They’ve been around a long time. The first flaw has been present since nginx 1.9.5, released in 2015, which is why so many servers are in scope.
- No confirmed attacks yet. Reports say there is no evidence of exploitation so far. However, once a flaw is public, attackers tend to start looking for vulnerable servers quickly, so organisations shouldn’t wait.
- A fix exists. Fixed nginx versions are out, though some server operating systems take a little longer to publish their own update. As of 19th November, for example, Debian’s stable releases, which many servers run, had not yet received a fixed package.
General advice: does it affect my website?
This is the key question, and it depends on the server underneath your website, not on the website itself.
- If your site runs on a server using nginx with HTTP/2 enabled, it is potentially affected until the server is updated or HTTP/2 is turned off. Changing your own website, such as updating WordPress or your plugins, does not fix this, because the flaw is in the web server software, not in your site.
- If your site runs on a server that doesn’t use nginx, such as one using Apache or LiteSpeed, these two flaws don’t apply.
- If your hosting company manages the server, it’s their job to apply the fix, and you don’t need to do anything. It’s still worth checking their security announcements.
Not sure what your website runs on? Ask your host or web developer, or ask us.
General advice: what should you do right now?
If we host your website, you don’t need to do anything: see the section for O’Brien Media customers below. Otherwise:
- If you’re hosted elsewhere: ask your host whether they use nginx and whether they’ve applied the update or turned HTTP/2 off as a temporary measure. A good host will already have a response.
- If you run your own server: see the section for IT teams below.
- Whatever you use: keep your software up to date, and use strong, unique passwords with two-step verification.
- Be wary of emails about this. Scammers love using security news as bait for fake "urgent security update" messages. Don’t click links or open attachments you weren’t expecting, and go directly to your supplier’s website instead.
O’Brien Media customers: what we’ve done
This section only applies if we host your website. The servers we host websites on use nginx, so this does apply to us, and we’ve acted on it.
- HTTP/2 has been temporarily turned off on our hosting servers. With it off, neither flaw can be reached, which is also what the security researchers recommend until the software can be updated.
- Your website is being served over HTTP/1.1 in the meantime. It stays secure and online. Pages that load a lot of files may be a little slower, but most visitors won’t notice.
- You don’t need to do anything. Updating WordPress, plugins or your theme isn’t part of the fix, because the flaw is in the web server software and not in your website.
- When the fixed software is available for our servers, we’ll install it and switch HTTP/2 back on. The Linux version we run hadn’t yet published its fixed nginx package as of 19th November 2026, and we’ll update this post when it’s done.
Keeping servers patched is a routine part of managed hosting, and you can read more in how we keep the websites we host secure.
If you’d like to know more about how we look after websites, see our WordPress support and hosting services.
IT teams: technical details
If you manage nginx yourself, the details below come from the nginx project’s advisories page and the Wiz Research write-up. Always check the official advisories for your exact build.
- Affected: nginx 1.9.5 to 1.31.8 for CVE-2026-123007, and 1.19.7 to 1.31.8 for CVE-2026-123633. Both need HTTP/2 enabled.
- Fixed in: nginx 1.30.7 (stable) and 1.31.9 (mainline). For NGINX Plus, CVE-2026-123633 is fixed in 37.0.7.1 or 37.2.0.1, and CVE-2026-123007 in 37.0.8.1 or 37.3.0.1.
- If you can’t upgrade yet, temporarily disable HTTP/2. On nginx 1.25.1 or later, set http2 off; in the affected server blocks. On older versions, remove the http2 parameter from any listen directives. Test the configuration, reload nginx, and re-enable HTTP/2 once you’ve upgraded.
- If you use a distribution package (for example from Debian), check your distribution’s security tracker for its fixed version rather than relying on the upstream version number.
- Things to watch for: unexpected nginx worker crashes, commands being launched by nginx, and long-lived HTTP/2 connections sending large numbers of WINDOW_UPDATE frames. Wiz also notes that ASLR doesn’t protect against these bugs, and that a CDN or web application firewall that terminates HTTP/2 in front of your server may offer partial protection.
- Expect HTTP/1.1 in the meantime. Sites keep working, though pages that load many files may be slightly slower.
Frequently asked questions
What is the nginx HTTP/2 vulnerability?
It’s two separate critical security flaws, CVE-2026-123007 and CVE-2026-123633, in the part of nginx that handles HTTP/2 connections. In the worst case, they could let an attacker run their own commands on a vulnerable server. Fixed versions of nginx were released on 18th November 2026.
What is nginx?
nginx is popular web server software. It receives requests from visitors’ browsers and sends back your website’s pages, and is often used by hosting companies to make websites faster and handle more visitors.
Is my website affected?
It depends on your hosting. If your website is on a server running nginx with HTTP/2 enabled, the server may be affected until it’s updated. If your server uses different software, these two flaws don’t apply. Your host or developer can tell you which you have.
Do I need to update WordPress or my plugins?
Not because of these flaws. They’re in the web server software, so updating WordPress, plugins or your theme won’t fix them. You should still keep those updated for other reasons.
Is HTTP/2 the same as HTTPS?
No. HTTPS is the secure padlock connection that protects data between a visitor and your site. HTTP/2 is a faster way of delivering pages over that connection. Turning off HTTP/2 doesn’t turn off HTTPS, and your site stays secure.
Will my website break if HTTP/2 is turned off?
No, it should carry on working normally. Browsers fall back to the older HTTP/1.1, so some pages, especially those that load a lot of files, may load a little more slowly.
Are these flaws being used in real attacks?
As of 18th November 2026, no attacks had been reported. One research team says it has working exploits but is keeping them private. Because the flaws are public, organisations are urged to patch quickly rather than wait.
Do I need to do anything if O’Brien Media hosts my website?
No. We’ve temporarily turned HTTP/2 off on our servers, which stops both flaws being reached, and we’ll install the permanent fix and switch HTTP/2 back on once it’s available. Your website stays online and secure in the meantime.
Where can I read more?
The nginx project lists both flaws on its security advisories page, and the research team at Wiz has published a technical write-up, Unauthenticated Remote Code Execution in NGINX: CVE-2026-123633 and CVE-2026-123007. F5 has also published advisories K000163926 and K000163928.
Not sure if you’re affected?
If you’re worried about your own website or the server it runs on, we’re happy to check and give you a straight answer, with no jargon and no sales pitch. Contact us today or call 01793 239 239.


