If NGINX accepts HTTP/2 connections, check the server even if it only serves HTML. On November 18, 2026, NGINX released fixes for two flaws that can allow code execution without a login. The first upstream Open Source releases with both fixes are 1.30.7 (stable) and 1.31.9 (mainline). If you installed NGINX from your Linux distribution, check the package revision before deciding you are covered. NGINX security advisories.
A static site and a reverse proxy have different exposure
CVE-2026-123007: an error tracking how much data can be sent over HTTP/2 can corrupt the memory of the process handling the connection. The affected code dates back to NGINX 1.9.5. Wiz demonstrated remote code execution against a static HTTPS site with no backend application or third-party module. Wiz research.
CVE-2026-123633: in certain reverse proxy configurations, an NGINX worker running low on available connections can continue using memory it has freed. Upstream lists 1.19.7 as the first affected release. An HTTP/2 proxy in front of WordPress or an API warrants a check for both flaws; updating plugins or application code does not patch NGINX. CVE-2026-123633 · CVE-2026-123007.
Researchers demonstrated code execution for both flaws. That does not automatically grant root: the impact depends on which files, credentials and services the NGINX worker can access. At disclosure, the cited sources did not give a confirmed count of compromised servers. An unexpected worker crash deserves investigation but cannot identify either CVE on its own.
Which NGINX versions fix both CVEs?
| Installation | What to look for |
|---|---|
| NGINX Open Source | 1.30.7 on stable or 1.31.9 on mainline, or a later release on the corresponding branch. |
| NGINX Plus | 37.0.8.1 or 37.3.0.1, depending on the branch. Versions 37.0.7.1 and 37.2.0.1 fix the proxy flaw but not the one affecting static sites. |
| Distribution package | Look for the package revision marked fixed for both CVEs on your distribution release. It may retain an older base version. |
Release details: NGINX security advisories · Rapid7 fix table.
Ubuntu status checked November 18: Canonical still listed packages for 22.04, 24.04 and 26.04 LTS as vulnerable. Its notes also identify older 22.04 proxy configurations accepting cleartext HTTP/2. Do not rule that case out just because the base version predates 1.19.7. Check the current status of both records: CVE-2026-123007 · CVE-2026-123633.
How to check your VPS without testing an attack
Run these checks on the instance or container that receives traffic. The first command identifies the binary; the second tests the configuration on disk and displays relevant directives. If the service uses a custom configuration, specify the same file with -c. Do not share the full configuration dump.
Managing your own reverse proxy?
Explore TERAMONT VPS options for hosting NGINX and your applications.


nginx -v
sudo nginx -T 2>&1 | grep -E '^[[:space:]]*(http2|listen|proxy_pass|fastcgi_pass|grpc_pass)[[:space:]]|test (is successful|failed)'Look for http2 on; or an http2 parameter on a listen directive. Identify the server block and any inherited settings before interpreting a match. If the test fails, empty output is not evidence of protection. On Ubuntu, apt-cache policy nginx shows the installed and candidate revisions; a match does not prove the repository has shipped the fix.
CDN example: seeing h2 in a browser only confirms HTTP/2 between the visitor and the CDN. If the CDN talks to NGINX over HTTP/1.1, also check whether any client can reach an HTTP/2 listener on the origin directly. If NGINX accepts no HTTP/2 connections on any path, a prerequisite for both CVEs is absent.
How to mitigate now and verify the rollout
If no patch is available yet, identify services that rely on HTTP/2, such as gRPC, before disabling it. On NGINX 1.25.1 and later, use http2 off; in affected blocks and remove the legacy http2 parameter from any listen directives enabling it. On older versions, change the listener rather than adding a directive the binary cannot understand. Back up the configuration, validate with nginx -t and reload only after the test passes. Confirm the old workers have exited. NGINX HTTP/2 directive.
Once a fixed revision is available, install it from your package channel and restart the service during your maintenance window, or redeploy every replica with the patched image. Reloading configuration alone does not replace the running binary. Check each instance, request a page and a backend route, and verify gRPC clients before closing the change.
If another team manages ingress, ask two questions: which component accepts HTTP/2, and which patched build is running there? For more on the role of that proxy, see our NGINX vs. Traefik comparison.







