Unauthenticated remote code execution in Nginx
- ID
- 47973
- Status
- summarized
- Published
- 18 Nov 2026, 11:19 PM
- Fetched
- 19 Nov 2026, 5:09 AM
- Provider
- Hacker News
- Category
- dev-community
- Original URL
- https://www.wiz.io/blog/nginx-http2-rce-vulnerabilities
- Source URL
- https://hnrss.org/best
Summary
- Score
- 8.5
- Created
- 19 Nov 2026, 5:10 AM
- Tags
- Audience
- developersvibe_coderssaas_founders
What happened
Wiz Research, alongside Ikotas Labs, Metnir, Rapid7 and Xint, disclosed two critical NGINX flaws — CVE-2026-123633 and CVE-2026-123007 — both rated CVSS 4.0 9.2, allowing unauthenticated remote code execution, with one chain confirmed including an ASLR bypass. Both require HTTP/2 to be enabled, and CVE-2026-123007 affects versions back to NGINX 1.9.5 from 2015; F5 shipped fixes in its November 18, 2026 security release. The report notes NGINX fronts more than 225 million websites, so exposure is broad and independent of whether your own application code is secure.
Why it matters
If you terminate TLS at NGINX yourself — VPS, bare metal, self-managed Kubernetes ingress, Docker base images — check your version and whether HTTP/2 is on, then move to the November 18, 2026 release. Because both CVEs require HTTP/2, turning it off on an unpatched box is the obvious stopgap while you schedule the upgrade; a CDN or load balancer in front does not protect a vulnerable NGINX origin behind it. Also check pinned base images and Helm charts, since a version from 2015 onward is in scope for CVE-2026-123007.
Discussion angle
Do you actually know which NGINX version and HTTP/2 setting is running across your fleet right now — and if not, what's the fastest way to find out before the next deploy cycle?