---
title: "NGINX vulnerability CVE-2026-123633: is your website affected?"
description: "NGINX is fixing a critical HTTP/2 vulnerability rated CVSS 9.2. Any website, e-shop or application served through NGINX can be exposed. What to do today."
canonical: "https://interfase.sk/en/news/nginx-vulnerability-cve-2026-123633-is-your-website-affected"
lang: "en"
last_updated: "2026-11-19"
---

# NGINX vulnerability CVE-2026-123633: is your website affected?

> NGINX is fixing a critical HTTP/2 vulnerability rated CVSS 9.2. Any website, e-shop or application served through NGINX can be exposed. What to do today.

Published: 2026-11-19

- NGINX has fixed critical HTTP/2 vulnerability CVE-2026-123633, rated CVSS 9.2. The fix is in versions 1.30.7 and 1.31.9.
- Any NGINX serving HTTP/2 to clients and passing requests on to an application is exposed – that is most websites, e-shops and reverse proxies.
- An up-to-date WordPress, e-shop or custom application does not protect you; the NGINX version in front of it is what counts.
- The full seven-step process and a temporary workaround are in the Cybair article.

NGINX has disclosed a critical vulnerability, CVE-2026-123633, in its HTTP/2 handling. On 18 November 2026 the NVD rated it CVSS 9.2 out of 10. An attacker can exploit it over the network without logging in and, in the worst case, crash the server or run their own code on it. The fix is in NGINX 1.30.7 and 1.31.9.

We have written up the full process, the affected versions and a temporary workaround on the website of our security division Cybair: [Critical NGINX vulnerability CVE-2026-123633 in HTTP/2: what to do now](https://cybair.sk/en/news/critical-nginx-vulnerability-cve-2026-123633).

## Is your website affected?

Very likely. NGINX sits in front of a huge share of websites – as a web server, reverse proxy or load balancer. It is exposed if it serves HTTP/2 to clients and passes requests on to an application. That is a common setup today.

The flaw is not in WordPress, your e-shop or your custom application, but in the NGINX in front of them. So a fully up-to-date website can be exposed too. The same applies when the application runs on Apache or IIS and NGINX only sits in front of it.

The easiest places to forget are the less visible ones: Kubernetes ingress controllers, container images, OpenResty and network appliances with NGINX inside. These need a fixed build from their vendor.

## Why not to put it off

None of the primary sources has confirmed exploitation in the wild so far. But NGINX source code is public and the fix shows where the flaw is. Sites left on an old version will sooner or later become a target of automated scans.

## What to do today

1. List every server, proxy, load balancer and container running NGINX, test ones included.
2. For each, check the NGINX version and whether HTTP/2 is enabled.
3. Agree with your hosting provider or server administrator on an update to 1.30.7 or 1.31.9, or a fixed distribution package.
4. Restart NGINX after the update. A reload alone does not start the new binary.

How to check the configuration, why NGINX and the NVD rate the flaw differently, and how to disable HTTP/2 temporarily if you cannot update right away is covered in the [guide to the NGINX vulnerability CVE-2026-123633 on Cybair](https://cybair.sk/en/news/critical-nginx-vulnerability-cve-2026-123633).

## Need help?

The Cybair security team will check NGINX across all your servers and infrastructure, deploy the fix directly in your environment and verify that the vulnerability is gone. You can reach us through the [form in the Cybair article](https://cybair.sk/en/news/critical-nginx-vulnerability-cve-2026-123633#form).


---

Web version: https://interfase.sk/en/news/nginx-vulnerability-cve-2026-123633-is-your-website-affected
llms.txt: https://interfase.sk/llms.txt
