News · Security · November 21, 2026
Two NGINX HTTP/2 flaws: upgrade to 1.30.7 or 1.31.9
F5 rates two NGINX HTTP/2 flaws Critical (CVSS 4.0: 9.2). Check your version with nginx -v and upgrade to 1.30.7 or 1.31.9.
DRIVE 369 DAO · 4 min read
On 18 November 2026 F5 and the NGINX project disclosed two memory-safety flaws in NGINX's HTTP/2 handling: CVE-2026-123007 and CVE-2026-123633. F5 scores each High (8.1 on CVSS 3.1) and Critical (9.2 on CVSS 4.0). Both are fixed in NGINX Open Source 1.30.7 (stable) and 1.31.9 (mainline). If you run NGINX with HTTP/2 on, check your version with nginx -v and upgrade.
You may have seen the flaws described as letting any unauthenticated attacker run code on your server. F5's advisories are narrower. They say an attacker can crash a worker process or corrupt its memory, and that code execution is possible, not certain: it needs a system with ASLR (address space layout randomization) disabled, or an attacker who can bypass it. The advisories we read do not say anyone is exploiting either flaw.
What the advisories say
| Question | CVE-2026-123007 | CVE-2026-123633 |
|---|---|---|
| What is the flaw? | HTTP/2 flow control: the window can exceed its allowed limit, which can cause a heap buffer overflow, usually followed by a worker crash (CWE-191, integer underflow) | A use-after-free in a worker process when HTTP/2 client requests are proxied to a backend and the worker runs low on worker_connections |
| Impact, in F5's words | Crash the worker, corrupt its memory, or potentially execute code remotely | A denial of service, or possibly code execution |
| When can code run? | With ASLR disabled, or if the attacker can bypass ASLR | Same condition |
| Score | High 8.1 (CVSS 3.1), Critical 9.2 (CVSS 4.0) | Same |
| NGINX Open Source affected | 1.9.5 to 1.30.6 and 1.31.0 to 1.31.8 | 1.19.7 to 1.30.6 and 1.31.0 to 1.31.8 |
| NGINX Open Source fixed | 1.30.7 and 1.31.9 | 1.30.7 and 1.31.9 |
| NGINX Plus affected | 37.0.0 to 37.0.7.1 and 37.1.0 to 37.2.0.1 | 37.0.0 to 37.0.6.1 and 37.1.0 to 37.1.1 |
| NGINX Plus fixed | 37.0.8.1 and 37.3.0.1 | 37.0.7.1 and 37.2.0.1 |
| Mitigation listed by F5 | None | None |
Sources: F5 advisories K000163926 and K000163928, both published 18 November 2026 and updated 19 November; the NGINX security advisories list the same versions. All primary, as of 21 November 2026.
Two things the sources do not agree on or do not say:
- Severity labels differ. nginx.org marks CVE-2026-123633 "medium" and CVE-2026-123007 "major" on its own scale. F5 gives CVSS scores. A score measures how bad a flaw could be, not how likely an attack is.
- Exploitation is not reported. Neither advisory says the flaws are used in attacks. We also looked at the first page of CISA's Known Exploited Vulnerabilities catalog on 21 November and found no NGINX entry; we could not check the other pages.
The tiers, from the lowest we can prove: exposed (any NGINX in the affected ranges with HTTP/2 on), exploited (not reported), confirmed compromised (none known).
What to do this week
- Find every NGINX you run. Web servers, load balancers, containers and Kubernetes ingress. F5 also lists NGINX Instance Manager, F5 WAF for NGINX, NGINX Gateway Fabric and NGINX Ingress Controller as affected for CVE-2026-123007; read the advisory for their fixed versions (for example Instance Manager 2.25.0 and Gateway Fabric 2.9.0).
- Check the version with
nginx -v. If it is in the ranges above, upgrade to 1.30.7 or 1.31.9 (or newer) from nginx.org. - Restart NGINX so the patched program is the one running.
- In containers, rebuild from the patched base image and check the digest of the image that is running, not only its label.
- On a Linux distribution package, read your distribution's advisory. Distributions often fix a flaw without changing the upstream version number, so the number alone may not tell you.
- If you cannot upgrade today, know that F5 lists no mitigation. A hosting provider's customer notice suggests switching HTTP/2 off for now:
http2 off;in the server block on NGINX 1.25.1 or later, and remove thehttp2parameter fromlistenlines. We could not confirm that on F5's pages, so test it, reload, check that the old workers have exited, and turn HTTP/2 back on only after the upgrade.
The same notice says the flow-control flaw was shown on a server that only serves static files. We could not find that in F5's advisories either, so treat any NGINX with HTTP/2 on as in scope.
Ghostdrive angle
This one is not about us. It is about the web servers you run, and nothing we build patches them for you. What Ghostdrive can add on the testnet (audit pending) is that files are sealed on your device before they reach any server, so a compromised server holds ciphertext. That limits the damage; it does not stop the server being compromised.
Limits
We read the two F5 advisories, the NGINX advisory list and its change log. We did not test either flaw and did not read the code. F5 says it is still researching some products and will update the articles, so check them again before you close the ticket.
Questions
- Can an attacker run code on my server with these flaws?
- F5 says code execution is possible, not certain: it needs a system with ASLR disabled or an attacker who can bypass it. The flaws can also crash a worker process or corrupt its memory. Neither advisory says they are exploited.
- Am I affected if HTTP/2 is off?
- F5 describes both flaws as affecting NGINX configurations that use HTTP/2. If HTTP/2 is off on a server, the advisories do not put it in scope. Upgrade anyway, so that turning HTTP/2 on later is safe.
- Which versions fix them?
- NGINX Open Source 1.30.7 (stable) or 1.31.9 (mainline), or newer. For NGINX Plus, 37.0.8.1 or 37.3.0.1 fixes CVE-2026-123007, and 37.0.7.1 or 37.2.0.1 fixes CVE-2026-123633.