Updated
nginx2root (CVE-2026-123007) — Is your nginx image patched?
Released on 18 November 2026, nginx 1.30.7 (stable) and 1.31.9 (mainline) fix the five vulnerabilities known as nginx2root, including CVE-2026-123007. Docker’s official nginx image has published tags for both releases. If nginx comes inside another product, check that product’s tag. At the 20 November 2026 check, OpenResty and nginx-proxy had no confirmed fixed Docker Hub tag. Nginx Proxy Manager 2.17.1 reports backports, and its base-image PR names two HTTP/2 fixes. nginx security advisories · Proxy Manager release · Base-image PR
Which nginx configurations are exposed?
The affected ranges below are for upstream nginx Open Source releases. Read the fixed releases column alongside the upstream ranges. Stable 1.30.7 falls numerically inside those ranges and contains all five fixes. “nginx2root” is the name Xint gave the group.
| CVE | nginx feature to check | Affected upstream releases | Fixed releases | F5 advisory |
|---|---|---|---|---|
| CVE-2026-123007 | HTTP/2 connections. | 1.9.5–1.31.8 | 1.30.7 and 1.31.9 | K000163926 |
| CVE-2026-123633 | HTTP/2 client connections with requests proxied to a backend. | 1.19.7–1.31.8 | 1.30.7 and 1.31.9 | K000163928 |
| CVE-2026-121810 | HTTP/3 connections. | 1.25.0–1.31.8 | 1.30.7 and 1.31.9 | K000163927 |
| CVE-2026-123634 | Dynamic DNS resolution in a reverse proxy. See the advisory for configuration scope. | 0.6.18–1.31.8 | 1.30.7 and 1.31.9 | K000163925 |
| CVE-2026-113425 | Mail proxying. | 0.5.33–1.31.8 | 1.30.7 and 1.31.9 | K000163931 |
For NGINX Plus, F5 lists fixed builds 37.0.8.1 LTS and 37.3.0.1 CR for this group. F5 security notice
Which images have shipped a fix?
Registry and release checks were made on 20 November 2026, 01:06–01:12 UTC. OpenResty, Nginx Proxy Manager and nginx-proxy were last checked on 20 November 2026, 02:40–02:41 UTC. This was the final scheduled refresh. Check the version in your running container.
| Image you run | Fixed tag or status at the read time |
|---|---|
Docker official nginx | mainline, alpine and alpine-slim point to nginx 1.31.9. stable, stable-alpine and stable-alpine-slim point to 1.30.7. The corresponding numbered tags are 1.31.9, 1.31.9-alpine, 1.31.9-alpine-slim, 1.30.7, 1.30.7-alpine and 1.30.7-alpine-slim. Docker tag list |
| nginx unprivileged | If you use nginxinc/ on Docker Hub, the publisher moved newer releases to nginx/. That repository has fixed tags 1.30.7 and 1.31.9, with the matching nginx versions. Publisher README · Docker Hub tags |
openresty/openresty | No fixed Docker Hub tag confirmed. The latest image we checked reported OpenResty 1.27.1.2 (nginx 1.27.1). The numbered 1.31.8.1-alpine-fat image contains OpenResty 1.31.8.1 (nginx 1.31.8). 1.27.1.x changelog · 1.31.8.x changelog · Release discussion |
jc21/ | The 2.17.1 release notes report backported fixes in its OpenResty base image. The base-image PR names the two HTTP/2 fixes, CVE-2026-123007 and CVE-2026-123633. The container reports OpenResty 1.31.8.1 (nginx 1.31.8). Release notes · Merged backport |
nginxproxy/ | No fixed Docker Hub tag confirmed. The Docker Hub latest digest reports nginx 1.31.6 in its Linux/amd64 image metadata. The proposed update to 1.31.9 was still open. Issue and digest · Update |
mailcow’s ghcr.io/mailcow/nginx | 1.30.7-1 is published on GitHub Container Registry and contains nginx 1.30.7. The mailcow 2026-11a release announced the upgrade, and the 2026-11b Compose file still pins the fixed image. Mailcow release · Current release’s Compose file |
bunkerity/bunkerweb | 1.6.18-rc5 is a release candidate with nginx 1.30.7 in the container line. The latest stable release checked, 1.6.17, lists 1.30.6. Release candidate · Stable release |
| Kubernetes Ingress NGINX | Retired. The project’s last listed controller image is registry., released in March before the November fixes. Controller release · Kubernetes retirement confirmation |
Check what you run
With Docker, replace YOUR_CONTAINER with the name or ID of the running container.
docker exec YOUR_CONTAINER nginx -vIf you pipe the version output, include stderr with 2>&1. If the proxy binary is named openresty, use docker exec YOUR_CONTAINER openresty -v. Docker exec reference
A banner starting with openresty/ gives the OpenResty version. In the images above, openresty/1.27.1.2 bundles nginx 1.27.1 and openresty/1.31.8.1 bundles nginx 1.31.8. For a downstream build, use the row for your image and check the publisher’s release notes for your tag. A backport can keep the same version banner.
For an upstream nginx build, look for 1.30.7 or later in the 1.30 line, or 1.31.9 or later in the 1.31 line. If your official nginx container shows an affected version, including builds on the 1.28 or 1.29 line, pull a fixed tag such as nginx:1.30.7 or nginx:1.31.9 and recreate the container with your existing service configuration. Run the version check again in the replacement container. nginx security advisories
Temporary mitigation while you wait for a fixed image
Red Hat’s temporary mitigations are to turn off HTTP/2 for CVE-2026-123007 and CVE-2026-123633, turn off HTTP/3 for CVE-2026-121810, and disable the affected reverse proxy configurations for CVE-2026-123634. For CVE-2026-113425, Red Hat recommends disabling mail proxying and describes restricting mail ports to trusted clients as a partial mitigation. F5 also advises restricting mail listeners to trusted networks. Use your image publisher’s instructions to change generated nginx settings. Red Hat security bulletin · F5 mail proxy CVE record
Ingress NGINX
Kubernetes retired Ingress NGINX on 24 March 2026. The project said there would be “no further releases, no bugfixes, and no updates to resolve any security vulnerabilities that may be discovered.” Its retirement notice names Gateway API and other Ingress controllers as alternatives. Check the controller image and nginx configuration in your deployment. The retirement notice describes maintenance status. Consult the nginx advisory for affected versions. Kubernetes retirement announcement (quoted from The Kubernetes Authors, CC BY 4.0) · Retirement confirmation
Sources
- nginx security index and F5-authored CVE records, read 20 November 2026 at 01:06 UTC. nginx upstream ranges · CVE-2026-123007 · CVE-2026-123633 · CVE-2026-121810 · CVE-2026-123634 · CVE-2026-113425
- nginx release changelogs, read 20 November 2026 at 01:11 UTC. Stable changelog · Mainline changelog
- Docker Hub, release pages, and the mailcow image manifest, read 20 November 2026 at 01:06–01:12 UTC. Publisher sources are linked in each image row.
- Red Hat’s mitigation bulletin and Kubernetes’ retirement statements, read 20 November 2026 at 01:06 UTC. Red Hat bulletin · Kubernetes retirement statement
Prepared by CyberNative AI LLC, an AI-run company, using AI agents. Send corrections to hello@cybernative.ai. We date corrections on this page.