NGINX HTTP/2 Vulnerabilities (CVE-2026-123633 and CVE-2026-123007): Security Advisory
Overview
Two critical security vulnerabilities, CVE-2026-123633 and CVE-2026-123007, have been disclosed in NGINX's HTTP/2 implementation.
Both vulnerabilities could allow an unauthenticated attacker to execute code remotely on an affected NGINX server, potentially leading to unauthorized access, data exposure, or service disruption.
The vulnerabilities are rated Critical (CVSS v4.0: 9.2) and affect NGINX Open Source, NGINX Plus, and potentially other products that include vulnerable NGINX versions.
Both vulnerabilities require HTTP/2 to be enabled, although additional conditions for exploitation differ.
Aqua Detection Coverage
Aqua detection update: Detection for CVE-2026-123633 and CVE-2026-123007 is now available in Aqua's Online CyberCenter vulnerability feeds:
- Online CyberCenter: Available now
- Offline CyberCenter: 02:40 UTC on November 19, 2026
Customers using Online CyberCenter can now rescan potentially affected NGINX images and use native vulnerability scanning and Image Assurance Policies to identify images with matching CVE findings.
Customers using Offline CyberCenter should rescan their images once the updated vulnerability content becomes available.
Important: Detection coverage may depend on the availability of vulnerability information from individual OS and package vendors. An image without a CVE finding should not automatically be considered unaffected. Customers should continue to verify their NGINX versions and configurations against the applicable vendor advisories.
These are estimated availability times and may change as updates are published.
Affected Versions and Available Fixes
| Product | CVE | Affected versions | Fixed versions |
| NGINX Open Source | CVE-2026-123633 | 1.19.7-1.30.6; 1.31.0-1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| NGINX Open Source | CVE-2026-123007 | 1.9.5-1.30.6; 1.31.0-1.31.8 | 1.30.7 (stable), 1.31.9 (mainline) |
| NGINX Plus | CVE-2026-123633 | R33-R36; affected 37.x releases | 37.0.7.1, 37.2.0.1 |
| NGINX Plus | CVE-2026-123007 | R33-R36; affected 37.x releases | 37.0.8.1, 37.3.0.1 |
Important: NGINX Plus R33-R36 do not have fixes available within those branches. Customers should upgrade to a supported release containing the appropriate security updates. For NGINX Plus, versions 37.0.8.1 or 37.3.0.1 address both vulnerabilities on their respective release tracks.
Additional Kubernetes and NGINX Products
Security research has also identified potentially affected deployments beyond standalone NGINX servers:
| Product | Current guidance |
| F5 NGINX Ingress Controller | Upgrade to version 5.8.0, which includes updated NGINX components. |
| NGINX Gateway Fabric | Upgrade to version 2.9.0, identified as containing the fixes. |
| Community Kubernetes ingress-nginx | The archived project includes vulnerable NGINX versions and has no planned security fix. Organizations should review HTTP/2 configuration and plan migration to a maintained alternative. |
| OS distribution packages and container images | Check the package or image provider's advisory for the applicable fixed release, including any backported security fixes. |
Customers using NGINX through Kubernetes ingress controllers, reverse proxies, container images, or third-party distributions should verify the underlying NGINX version and applicable vendor guidance.
Aqua Security Assessment
Aqua Security has completed its assessment of CVE-2026-123633 and CVE-2026-123007 and confirmed that Aqua products are not affected by these vulnerabilities.
No Aqua product updates or remediation are required.
Detection for both CVEs is now available in Aqua's Online CyberCenter, with Offline CyberCenter support expected shortly.
Customers running NGINX in their own environments should review their deployments for potentially affected versions, apply the appropriate vendor security updates, and rescan their images using Aqua to identify any matching vulnerability findings.
Recommended Actions
While Aqua completes its assessment, we recommend customers:
- Identify affected deployments: Review NGINX servers, container images, reverse proxies, and Kubernetes ingress controllers, prioritizing internet-facing services.
- Check versions and configuration: Compare installed NGINX versions against the affected ranges above and confirm whether HTTP/2 is enabled.
- Apply available fixes: Upgrade to the appropriate patched NGINX release or follow the security guidance provided by your OS or product vendor.
- Consider temporary mitigation: If upgrading is not immediately possible, consider disabling HTTP/2 on affected NGINX listeners. Test application compatibility first, particularly for services that depend on HTTP/2, such as gRPC.
- Verify remediation: Restart or redeploy affected services after updating, confirm the running NGINX version, and review vulnerability scan results as detection information becomes available.
Important: The absence of a CVE finding does not necessarily mean a workload is unaffected. Customers should validate their NGINX versions, HTTP/2 configuration, and vendor-provided security updates.
Additional Resources
[2] F5 Security Advisory - CVE-2026-123007
[3] F5 Security Advisory - CVE-2026-123633
Did you find it helpful? Yes No
Send feedback