Resources › CVE intelligence › nginx2root
nginx2root
CVE-2026-123007 · CVE-2026-123633
Verdict
nginx2root is two memory-corruption bugs in nginx's HTTP/2 code, reachable without authentication. A machine is exposed when HTTP/2 is on for a listener an attacker can reach; CVE-2026-123633 also needs a request that opens an outbound connection. Fixed in nginx 1.31.9 and 1.30.7, but distribution builds keep older version numbers, NGINX Plus has a release that fixes only one of the two, and builds older than 1.19.7 serving cleartext HTTP/2 are exposed despite the official range.
Does it reach you?
CVE-2026-123007 = requirements 1 and 2. CVE-2026-123633 = all three. If any one is false for a machine, it's out for that CVE.
| Requirement | How to check it | Rules a machine out when |
|---|---|---|
| 1. The build lacks the fix | The build itself, not the version string (table below) | The fix is in the build: nginx 1.31.9, 1.30.7 and later, or a distribution build carrying it. For CVE-2026-123633, builds older than 1.19.7 are out only if every HTTP/2 listener uses TLS |
| 2. HTTP/2 is on for a listener an attacker can reach, over TLS or cleartext | nginx -T: http2 on; or listen … http2 in any server on that address and port | HTTP/2 is off on every listener of the running nginx. Every major distribution and nginx.org package builds the HTTP/2 module in, so it's a configuration question |
| 3. CVE-2026-123633 only: a request opens a new outbound connection | nginx -T: any *_pass (proxy, FastCGI, gRPC, uwsgi, SCGI, memcached), a resolver, auth_request, mirror, or Lua and njs sockets | The HTTP/2 servers only serve static files and run no module that connects out. Not just proxy_pass: every outbound connection takes the same path |
Not required, so these don't rule a machine out: serving static files only (enough for CVE-2026-123007), TLS (cleartext HTTP/2 reaches the memory fault too), ASLR (each published exploit gets around it), a nearly full connection table (an attacker can fill it), stream, buffer and rate limits, or the bandwidth figures from one published exploit, which its authors say aren't a minimum.
Are you actually fixed?
Fixed versions by build. Where a version number misleads, the row says so.
| Build | Status as of 19 November 2026 |
|---|---|
nginx 1.31.9, 1.30.7 and later; official nginx images on those tags | Fixed |
| nginx 1.9.5 to 1.31.8 | Not fixed. CVE-2026-123633 officially starts at 1.19.7, but older builds serving cleartext HTTP/2 reach the same bug; version-range scanners call them "not affected" |
| Builds taken from nginx's source between 17 September and 29 October | Half fixed: CVE-2026-123633 only |
| NGINX Plus 37.0.8.1, 37.3.0.1 | Fixed |
| NGINX Plus 37.0.7.1, 37.2.0.1 | CVE-2026-123007 not fixed; these fix CVE-2026-123633 only |
| NGINX Plus R34 to R36 | Not fixed |
| Debian 12 bookworm 1.22.1-9+deb12u11 (DLA-4918-1), 13 trixie 1.26.3-3+deb13u11 (DSA-6642-1), sid 1.30.6-4 | Fixed, under version numbers in the "vulnerable" range |
| Debian forky 1.30.6-3 | Not fixed (sid's 1.30.6-4 is) |
| Debian 11 bullseye | Not fixed in the regular security archive; fixed only in paid extended support (ELA-1894-1), which also covers Debian 10 |
| Ubuntu 22.04, 24.04, 26.04, 26.10 (USN-9159-1); 16.04 to 20.04 with Ubuntu Pro | Fixed |
| RHEL 8, 9 and 10, including module streams; CentOS Stream 9 and 10; Rocky; Oracle Linux | Not fixed yet |
| AlmaLinux 9 base nginx (ALSA-2026:A025), AlmaLinux 10 (ALSA-2026:A024) | Fixed, ahead of Red Hat: the same version without .alma is not. AlmaLinux 8 and the Alma 9 1.24 and 1.26 streams: not fixed |
| Amazon Linux 2023, Amazon Linux 2 (nginx1), AL2027 preview | Fixed (1.30.7) |
| Alpine 3.21 to 3.24 | Fixed |
| SLES 15 SP4 to SP7, SLES 16, openSUSE Leap | Not fixed yet; openSUSE Tumbleweed 1.31.9 is fixed |
| Fedora 43 and 44 (1.30.6-2) | Not fixed in the stable updates |
Docker Hub nginxinc/nginx-unprivileged:latest | Not fixed: still 1.31.7 from 19 October. Use ghcr.io/nginx/nginx-unprivileged, which has the fixed tags |
Official nginx:perl | Not fixed when we checked; pull 1.30.7-perl or 1.31.9-perl |
| Kubernetes ingress-nginx | Not fixed, and won't be: the project is archived and bundles nginx 1.27.1. Patched forks exist (Chainguard's) |
| AKS application routing add-on | Not fixed yet |
| F5 NGINX Ingress Controller 5.8.0 and 2026-lts-r11, NGINX Gateway Fabric 2.9.0 | Fixed. BIG-IP, BIG-IP Next for Kubernetes and CNF: not affected |
| OpenResty, Tengine | Not fixed in any release; the fixes are in their source only |
| Angie, freenginx | Not fixed: neither fix in their public source |
Check your own machines
# 1. Which nginx, and is the HTTP/2 module built in?
nginx -V 2>&1 | grep -o -E 'nginx/[0-9.]+|with-http_v2_module'
# 2. Is HTTP/2 on for any listener? (read the running config)
nginx -T 2>/dev/null | grep -n -E '^\s*(http2\s+on|listen\s.*\bhttp2\b)'
# 3. For CVE-2026-123633: does any request connect out?
nginx -T 2>/dev/null | grep -n -E '_pass\s|^\s*resolver\s|auth_request|mirror\s|_by_lua|js_'
Exposed to CVE-2026-123007 if the build is unfixed and step 2 finds a listener; to CVE-2026-123633 if step 3 also finds something in those servers. On a distribution package, check the package's changelog for the CVE IDs rather than the version number.
What holds until you patch
Turning HTTP/2 off closes both CVEs. F5's advisories say there's no mitigation; the researchers, Red Hat and CERT-EU recommend this one.
| Workaround | What it does | Trade-off |
|---|---|---|
http2 off; (1.25.1+) and http2 removed from every listen | Closes both CVEs | Clients fall back to HTTP/1.1. It must cover every server on each address and port, cleartext ones too. Existing workers keep their open connections until they finish after a reload. HTTP/3 listeners stay exposed to a separate bug fixed in the same releases (CVE-2026-121810) |
ingress-nginx: use-http2: "false" | The same, for the controller | Until you move to a patched fork or another controller |
| A CDN or load balancer in front | Protects only if it ends the client's HTTP/2 itself and nginx can't be reached any other way | TCP or TLS pass-through doesn't protect, nor does an origin reachable directly |
Stream, buffer and rate limits; more worker_connections | Nothing that rules a machine out | Each bug needs one stream or works through control frames those limits don't see |
What's happening now
- 18 November: nginx released 1.31.9 and 1.30.7 and F5 published its advisories; Wiz, Xint and Rapid7 published their research. The fixes had been public in nginx's source since 11 November.
- Exploitation: Rapid7 has published a working remote-code-execution exploit for CVE-2026-123007; Wiz and Xint report code execution and withhold theirs. Fake exploit repositories are circulating. No attacks reported in the wild, and neither CVE is in CISA's Known Exploited Vulnerabilities catalog as of its 18 November update.
- Severity: F5 scores both 9.2 (CVSS 4.0); nginx.org rates CVE-2026-123007 major and CVE-2026-123633 medium.
- Lagging: Red Hat and its rebuilds, SUSE, Fedora, Kubernetes ingress-nginx, OpenResty, Tengine, Angie and freenginx have no fixed release yet.
Updates
- 20 November 2026: published.
Sources
- Fixes and advisories: nginx security advisories · F5 K000163926 (CVE-2026-123007) · F5 K000163928 (CVE-2026-123633) · CVE-2026-123007 · CVE-2026-123633
- Research: Wiz · Xint · Rapid7 · Cloudflare
- Distributions: Debian · Ubuntu · Red Hat RHSB-2026-019 · CERT-EU 2026-022
- Exploitation: CISA KEV