The nginx team shipped versions 1.30.7 (stable) and 1.31.9 (mainline) on November 18 with fixes for ten vulnerabilities. Two of them are in HTTP/2, and researchers at Wiz describe them as unauthenticated remote code execution. If you run nginx anywhere, even on a small VPS, upgrade today.
What exactly was fixed in nginx
According to the announcement on nginx.org, the new releases close ten CVEs at once. The two most serious ones are in HTTP/2:
- CVE-2026-123007: a flow control window overflow in HTTP/2. The 1.31.9 changelog says an attacker can crash a worker process or cause other damage. Versions 1.9.5 through 1.31.8 are affected, which means everything since 2015.
- CVE-2026-123633: a use-after-free in HTTP/2 that happens when free
worker_connectionsslots run out. Affected versions: 1.19.7 through 1.31.8.
On its security advisories page, nginx rates the first bug as "major" and the second as medium. Wiz Research takes a harder line: it gives both a CVSS 4.0 score of 9.2 and says they allow code execution on the server without authentication. According to Wiz, CVE-2026-123007 works with the default configuration, and the researchers demonstrated it on a 64-bit system that only served static files over HTTPS. The second bug requires nginx to run as a proxy in front of an application. The commercial NGINX Plus got fixes too, in releases 37.0.8.1 and 37.3.0.1 according to Wiz.
The other fixes cover HTTP/3 (CVE-2026-121810), the DNS resolver, the mail proxy module, an infinite loop while reading a request body over TLS 1.3, and a buffer overflow when the alias and try_files directives are combined (CVE-2026-125283). Release 1.31.9 also changes two behaviours: it now rejects header lines without a colon and requests whose chunked body carries too much framing overhead.
What to do now
The simplest path is to upgrade to 1.30.7 or 1.31.9 (or to the patched package from your Linux distribution or Docker image). Wiz also gives a workaround for when the upgrade has to wait: on nginx 1.25.1 and later, set http2 off; in your server blocks, remove the http2 parameter from listen directives, reload the configuration and check that the old worker processes have exited. Turn HTTP/2 back on after upgrading, because it makes pages load faster.
The timeline in the Wiz post shows what coordinated disclosure looks like in practice. The first bug reached F5 (the company behind nginx) on October 21, a patch was ready for review on November 10, and publication came together with the November 18 release. Our sources mention no attacks so far, but the technical write-up is public, so I would not wait.
What this means if you are learning to code
nginx sits in front of a huge share of the applications on the internet, often as a reverse proxy for Node.js, NestJS or Python. Even if you only write backend code, your first deployment will almost certainly involve an nginx.conf file. It pays to know what is in it: nginx -v prints the version, and nginx -t tests the configuration before you reload.
This story also teaches a habit that helps in every project: update your dependencies (server, runtime, libraries) on a schedule, not only when something breaks. If you are building an API in the NestJS course, add a check of your tools' security advisories to your deployment checklist. If you would rather have a simpler server with automatic HTTPS, read our piece on Caddy. And to catch vulnerable patterns in your own repository, a static scanner such as Semgrep is worth a look.
You do not need to understand how HTTP/2 flow control works to protect yourself. You need to know where to find the advisories and how to check your version.
Also today
- Java4Shell in OpenJDK. Calif described CVE-2026-114938, a bug in the HotSpot accelerated Base64 decoder on x86-64 CPUs with AVX-512 VBMI, present since OpenJDK 17.0.6. Patches shipped on November 17, and the
-XX:-UseBASE64Intrinsicsflag works as a stopgap. Calif - Ruby 4.0.10, 3.4.13 and 3.3.14. The new releases fix seven vulnerabilities in
Regexpand in string case conversion, and some of them may lead to code execution. CVE ids have been requested but not yet assigned. ruby-lang.org - Angular 22.3.0. The router gains route error boundaries,
HttpClienthas a newquery()method for HTTP QUERY requests, and view transitions are now stable. Templates also accept the++and--operators. GitHub - VS Code 1.147. As experiments, you can schedule a chat request for later and keep several drafts, and in preview an agent can drive your Chrome or Edge browser. Visual Studio Code
- Next.js on its growing number of advisories. The team counted 6 security advisories in 2024, 14 in 2025 and 51 so far this year; 70% of the bugs were in code more than a year old. Since version 16.4,
next devandnext buildwarn you when you run a vulnerable version. Next.js - Gemini 4 Neon for developers. Google made the new model available in the paid Gemini API, Android Studio and Antigravity, at $3 per million input tokens and $15 per million output tokens, with a one million token context. Google reports 65.2% on Terminal-Bench 4.1. Google
Frequently asked questions
Is my nginx vulnerable to CVE-2026-123007?
Yes, if you run a version from 1.9.5 to 1.31.8 with HTTP/2 enabled. Check with nginx -v; the fixed releases are 1.30.7 and 1.31.9. Linux distributions often backport patches under an older version number, so check their advisories too.
How do I disable HTTP/2 in nginx until I can upgrade?
On nginx 1.25.1 and later, add http2 off; to your server blocks and remove http2 from the listen directives. Then run nginx -t, reload nginx, and turn HTTP/2 back on once you have upgraded.
Do the nginx bugs affect apps on Vercel or Netlify?
Those platforms do not ask you to configure nginx, so patching is their job. The bugs affect you directly when you run nginx yourself: on a VPS, in a Docker container or as a Kubernetes ingress.
Sources
- nginx-1.30.7 and nginx-1.31.9, nginx.org, 2026-11-18
- Changes with nginx 1.31.9, nginx.org, 2026-11-18
- nginx security advisories, nginx.org, 2026-11-18
- NGINX HTTP/2 RCE vulnerabilities, Wiz Research, 2026-11-18
- Java4Shell: RCE in OpenJDK when processing Base64, Calif, 2026-11-17
- Multiple vulnerabilities in Regexp and String case conversion, ruby-lang.org, 2026-11-18
- Angular 22.3.0, GitHub, 2026-11-18
- Visual Studio Code 1.147, Microsoft, 2026-11-18
- How we're using AI to make Next.js more secure, Next.js, 2026-11-17
- Introducing Gemini 4 Neon, Google, 2026-11-18
This article was prepared with the help of AI from primary sources and reviewed by the CodeWorlds editorial team.