Security check · free · no sign-up

Is your website vulnerable to
NGINX2Root?

On 18 November 2026, several security flaws were published in nginx, one of the most widely used programs for serving websites. Type your address and we’ll tell you what your website reveals about it.

Published on · Last updated: · By the Wakaris team

Possible results
  • Version older than the fix, with HTTP/2

    Your website publicly shows that it uses nginx version and offers HTTP/2. That version is older than fixed, the one that fixes NGINX2Root. Based on what it publishes, the website could be out of date. What to do: if you manage the server, follow the steps below; if not, send the email to your hosting provider.

  • Version equal to or newer than the fix

    Your website publicly shows that it uses nginx version, equal to or newer than fixed. Based on what it publishes, it would be up to date.

  • nginx without HTTP/2

    Your website uses nginx and doesn’t offer HTTP/2. The two serious NGINX2Root flaws can only be reached over HTTP/2, so they aren’t reachable from outside. It’s a temporary protection: the real fix is to update nginx, and then HTTP/2 can be turned back on.

  • Version maintained by your system

    Your website publicly shows that it uses nginx version and offers HTTP/2. nginx.org no longer fixes that branch: it’s only protected if your system (Debian, Ubuntu, Red Hat…) has installed its own fix, and that doesn’t change the version number. It can’t be told apart from outside: check it on the server or ask your hosting provider with the email below.

  • nginx detected, version hidden

    Your website uses nginx and offers HTTP/2, but the server doesn’t make the version public (that’s good practice). From outside there’s no way to know whether it’s up to date: check it on the server or ask your hosting provider with the email below.

  • No trace of nginx in the headers

    Your website doesn’t publicly show that it uses nginx. It may hide it, sit behind a CDN or use a different server. This isn’t a diagnosis: if you’re not sure, ask your hosting provider.

What NGINX2Root is: the 2026 nginx HTTP/2 flaws, explained clearly

nginx is the program that receives each visit and delivers the page on a huge number of websites. Several flaws have been found in how it handles HTTP/2 connections.

NGINX2Root is the name given to a batch of nginx flaws published on 18 November 2026. The two serious ones are in HTTP/2, a widely used protocol for delivering web pages. There is a public proof of concept with which someone, with no access and no password, manages to run their own commands on the server with nginx’s permissions. The next step, taking full control of the server (root), depends on a separate flaw in the system kernel. As of 19 November 2026 there is no confirmed exploitation. They are fixed in nginx 1.30.7 and 1.31.9.

CVE-2026-123007

An error in HTTP/2 flow control (the count of how much data can be sent over the connection) corrupts nginx’s memory. It affects versions 1.9.5 to 1.31.8.

CVE-2026-123633

When handling HTTP/2, nginx can keep using a part of memory it had already released. It affects versions 1.19.7 to 1.31.8.

The same batch includes a flaw of the same kind in HTTP/3 (CVE-2026-121810), which only affects servers that have HTTP/3 turned on.

This page explains what happened and what to do. It neither includes nor links to code for exploiting the flaws.

Does it affect my website? Affected and fixed nginx versions

If your website is served with nginx, offers HTTP/2 and the server hasn’t been updated since 18 November 2026, it could be exposed. You don’t need to know which version you have: the checker above gives you a first clue and, if it can’t be seen from outside, below you’ll find what to ask.

As a visitor to other websites, you can browse as usual. These flaws affect the server, not your computer or phone.

nginx versionFixed versionStatus
nginx 1.31.x (mainline branch)1.31.9Fixed by nginx.org
nginx 1.30.x (stable branch)1.30.7Fixed by nginx.org
Earlier mainline branches (1.29, 1.27…)No fixed version for that branchBest to move to 1.30.7, 1.31.9 or later
Earlier stable branches (1.28, 1.26, 1.24, 1.22, 1.18…)Whatever your system publishes, with the same numbernginx.org no longer fixes them · it depends on your distribution’s package
Debian 13 (nginx 1.26.3)No fixed package as of 19 November 2026Pending · meanwhile, the temporary measure below

For other distributions (Ubuntu, Red Hat, Alpine…), check each one’s security advisory: every distribution publishes its fix on its own, and this page can’t take it for granted.

An nginx that offers neither HTTP/2 nor HTTP/3 can’t be reached by these flaws even if it isn’t updated. It’s a temporary protection, not the fix.

What to do if someone else runs your website

You don’t have to touch anything. You have to ask. Copy this email and send it to your hosting provider or to whoever built your website:

Subject: Question about NGINX2Root (CVE-2026-123007 and CVE-2026-123633)

Hello,

My website [yourdomain.com] is hosted with you. On 18 November 2026, several nginx security flaws in HTTP/2 were published (CVE-2026-123007 and CVE-2026-123633), fixed in nginx 1.30.7 and 1.31.9.

Could you confirm:

1. Whether the server that delivers my website uses nginx.
2. Whether the fix is already installed.

3. If it isn’t, when you’ll install it and whether you’ve turned off HTTP/2 in the meantime.

Thank you.

If you don’t get a clear answer within 48 hours, that’s a sign in itself. A website needs someone to maintain it.

How to update nginx against NGINX2Root, step by step

The definitive fix is to update nginx. Turning off HTTP/2 only reduces the exposure in the meantime.

  1. Step 1 · Check your version and whether HTTP/2 is on

    On the server, see which version is running and whether the effective configuration turns on HTTP/2:

    nginx -v
    nginx -T 2>/dev/null | grep -n "http2"

    If you installed it with your system’s packages (apt, dnf), the fix will arrive that way and may come applied without the version number changing. If it comes from nginx.org or a Docker image, you need 1.30.7, 1.31.9 or later.

  2. Step 2 · Update to the fixed version

    1.30.7 (stable) or 1.31.9 (mainline), or your distribution’s fixed package once it’s published. Examples:

    # Debian / Ubuntu
    sudo apt update && sudo apt install --only-upgrade nginx
    
    # RHEL / AlmaLinux / Rocky
    sudo dnf update nginx

    With Docker, switch to a fixed image tag and recreate the container. As of 19 November 2026, Debian 13 hasn’t published its fixed package yet: if that’s your case, apply step 4 until it arrives.

  3. Step 3 · Restart nginx

    The update doesn’t count until the old processes stop serving connections. Check the configuration and restart:

    sudo nginx -t && sudo systemctl restart nginx
  4. Step 4 · If you can’t update yet: turn off HTTP/2 temporarily

    The two serious flaws can only be reached over HTTP/2. In every server block that has it turned on:

    # With the http2 directive:
    http2 off;
    
    # On older versions, remove "http2" from the listen line:
    listen 443 ssl;        # before: listen 443 ssl http2;

    Then run sudo nginx -t and restart nginx. Your website will keep working over HTTP/1.1; pages with many files may load a little more slowly. If you also have HTTP/3 turned on, consider turning it off too until you update. It’s a temporary measure and doesn’t replace the update.

  5. Step 5 · Once it’s updated, turn HTTP/2 back on

    With the fixed version installed and nginx restarted, undo step 4: HTTP/2 makes your website load better and there’s no reason to leave it off. Run the checker above again to see what your website publishes now.

The reliable check is done on the server

What this website reads from outside is a clue, not proof. This is what’s reliable:

# Which version is actually running?
nginx -v

# Does the system package include the fix? (look for the CVE in the changelog)
# Debian/Ubuntu:
apt changelog nginx | grep CVE-2026-123007

# Is HTTP/2 turned on in the effective configuration?
nginx -T 2>/dev/null | grep -n "http2"

Learn more

Frequently asked questions about NGINX2Root

What is NGINX2Root?

It’s the name given to a batch of nginx security flaws published on 18 November 2026. The two serious ones (CVE-2026-123007 and CVE-2026-123633) are in HTTP/2, and there is a public proof of concept that runs code on the server with nginx’s permissions. They are fixed in nginx 1.30.7 and 1.31.9.

How do I know if my website uses nginx?

Many websites say so in a header the server sends with every page; the checker on this page reads it. If your website doesn’t make it public, or sits behind a CDN, it can’t be seen from outside: ask your hosting provider or whoever built your website (there’s an email ready to copy further up).

Which nginx version is safe against NGINX2Root?

The versions fixed by nginx.org are 1.30.7 (stable branch) and 1.31.9 (mainline branch), or any later one. If your nginx comes from your system’s packages (Debian, Ubuntu, Red Hat…), what matters is that the package includes the fix: distributions patch without changing the version number.

Why does the result say my version is maintained by my system?

Because your website publishes a version from a branch nginx.org no longer fixes (1.28, 1.26, 1.24, 1.22, 1.18…). Those versions usually come from a distribution’s package, which applies its own fixes without changing the number. From outside, a patched server and an unpatched one look the same: it has to be checked on the server.

Will turning off HTTP/2 make my website stop working?

No. The website keeps working over HTTP/1.1; pages with many files may load a little more slowly. It’s a temporary measure: it protects against the two serious flaws until the update arrives, and HTTP/2 is turned back on as soon as nginx is fixed.

If my website doesn’t offer HTTP/2, is it already protected?

Against the two serious HTTP/2 flaws, yes: they can’t be reached from outside. But it isn’t the fix. The same batch fixes other nginx flaws that are only solved by updating, so it’s worth updating anyway.

Can someone take full control of the server?

The public proof of concept runs code with the permissions of the nginx user, not the administrator’s. Getting to administrator (root) depends on a second, different flaw in the system kernel. That’s why it’s worth keeping both nginx and the operating system up to date.

Is it safe to visit websites these days?

Yes. NGINX2Root affects the server where the website is hosted, not the computer or phone of whoever visits it. The sensible precaution is the usual one: be careful with what you type (passwords, cards) on small websites that might be slow to update.

Can Wakaris tell from outside whether my website is updated?

Only partly. If the server publishes an nginx.org version, it can be compared with the fixed one, and it’s always possible to see whether it offers HTTP/2. If it hides the version (good practice) or publishes a distribution package’s version, it can’t be determined from outside. That’s why the result is a clue and the reliable verification is done on the server.

What is Wakaris?

Wakaris is a website analysis tool by Bitanube Labs (Andorra). It analyzes a website across nine specialties (security, performance, presence, SEO, accessibility, legal, experience, artificial intelligence and marketing) and explains the findings in plain language, without jargon. Analyzing a page is free and needs no sign-up.

This is just one finding: your website has many more

NGINX2Root is a finding from the Security specialty. Wakaris analyzes your website across nine specialties (security, performance, accessibility, legal, SEO and more) and explains it clearly, without jargon. Free and no sign-up.