NGINX HTTP/2 vulnerabilities (CVE-2026-123633, CVE-2026-123007)
Resolved
Nov 19, 2026 at 3:17pm UTC
Resolved: We’ve released updated images with fixes for all applicable CVEs across all affected image repositories, including ingress-nginx-controller 1.15.16, which adds the resolver and HTTP/3 fixes, and the Harbor IAM Guarded and Longhorn images. We’ve delivered updated images to affected customer registries, and any remaining images will sync on the normal schedule.
Running containers don’t update on their own. Pull the updated image and redeploy. If you deployed ingress-nginx-controller 1.15.15 earlier, update to 1.15.16.
For fixed versions and update steps, see our knowledge base article. For questions, contact Support.
Affected services
Updated
Nov 18, 2026 at 10:41pm UTC
Identified: Since our last update, we’ve published updated images with fixes for all applicable CVEs across 58 image repositories, including the NGINX, NGINX Plus, OpenResty, Apache APISIX, and Kong images. They’ll become available in customer registries as delivery completes.
In progress:
ingress-nginx-controllerimages have the fixes for the two HTTP/2 CVEs. We’re finishing a release with the remaining applicable fixes for the resolver and HTTP/3 CVEs.- Harbor IAM Guarded and Longhorn images are still building.
For questions, contact Support.
Affected services
Updated
Nov 18, 2026 at 8:08pm UTC
Identified: Since our last update, fixed NGINX packages addressing five vulnerabilities are available: CVE-2026-123633, CVE-2026-123007, CVE-2026-123634, CVE-2026-121810, and CVE-2026-113425.
Exposure depends on configuration. The first two require HTTP/2 to be enabled; the others require resolver-driven proxying, HTTP/3, or the mail proxy. ingress-nginx-controller and Kong enable HTTP/2 by default.
In progress:
- NGINX (stable, mainline, and iamguarded) and NGINX Plus: We’re rebuilding affected images for delivery to customer registries.
ingress-nginx-controller1.15: Updated images are being rebuilt, with additional fixes to follow. The mail proxy vulnerability doesn’t apply.- OpenResty, Apache APISIX, and Kong: These bundle their own NGINX. We’re updating their patches to address the vulnerabilities that apply.
We’ll provide another update by November 18 at 22:00 UTC, or sooner when patched images are available. For questions, contact Support.
Affected services
Updated
Nov 18, 2026 at 6:14pm UTC
Identified: Deployments using our default NGINX configuration, which doesn’t enable HTTP/2, remain unaffected.
In progress:
- NGINX packages (stable, mainline, and iamguarded): Package updates are being finalized. Once published, we’ll rebuild affected images and deliver them to customer registries.
ingress-nginx-controller1.15: Fixes are in progress.- NGINX Plus: F5 has released a fix. Our package update is pending.
Until you can deploy a patched image, consider disabling HTTP/2 if you’ve enabled it.
We’ll provide another update by November 18 at 19:30 UTC, or sooner when patched images are available. For questions, contact Support.
Affected services
Created
Nov 18, 2026 at 5:13pm UTC
Identified: Two critical NGINX vulnerabilities disclosed on November 18 can allow unauthenticated remote code execution when HTTP/2 is enabled. Upstream fixes are available in NGINX 1.30.7 (stable) and 1.31.9 (mainline).
Our default NGINX configuration doesn’t enable HTTP/2, so deployments using that configuration aren’t exposed to these vulnerabilities. Chainguard Containers that include NGINX, such as cgr.dev/chainguard/nginx, haven’t yet been patched.
We’re updating affected NGINX packages and will rebuild affected images as updated packages become available.
Workaround: If you’ve enabled HTTP/2, consider disabling it until you can deploy a patched image.
We’ll provide another update by November 18 at 18:00 UTC, or sooner when patched images are available. For questions, contact Support.
Affected services