TL;DR: Two critical vulnerabilities in NGINX’s HTTP/2 implementation, CVE-2026-123633 and CVE-2026-123007, could allow unauthenticated attackers to execute code remotely on affected servers. Both vulnerabilities carry a CVSS v4.0 score of 9.2 and require HTTP/2 to be enabled. Organizations should identify affected NGINX deployments and apply available security updates immediately.
Aquasec products are not affected, and detection for both vulnerabilities is available in Aquasec’s Online and Offline CyberCenter vulnerability feeds to help customers identify potentially vulnerable container images.
What are the critical NGINX HTTP/2 vulnerabilities?
Two critical vulnerabilities have been disclosed in NGINX’s HTTP/2 implementation, potentially exposing affected servers to remote code execution (RCE) without authentication.
The vulnerabilities, CVE-2026-123633 and CVE-2026-123007, affect NGINX Open Source and NGINX Plus, as well as potentially other products that incorporate vulnerable NGINX versions.
Both vulnerabilities require HTTP/2 to be enabled, although the additional conditions required for exploitation differ. Successful exploitation could allow an attacker to gain unauthorized access to an affected server, potentially exposing sensitive data or disrupting services.
NGINX is widely used as a web server, reverse proxy and Kubernetes ingress component, making it important for organizations to assess deployments beyond standalone web servers.
Which NGINX versions are affected?
The affected versions and available fixes depend on the NGINX product and vulnerability.
| Product | Affected versions | Fixed versions |
| NGINX Open Source, CVE-2026-123633 NGINX Open Source, CVE-2026-123633 | 1.19.7 through 1.30.6 and 1.31.0 through 1.31.8 | 1.30.7 or 1.31.9 |
| NGINX Open Source, CVE-2026-123007 | 1.9.5 through 1.30.6 and 1.31.0 through 1.31.8 | 1.30.7 or 1.31.9 |
| NGINX Plus, CVE-2026-123633 | R33 through R36 and affected 37.x releases | 37.0.7.1 or 37.2.0.1 |
| NGINX Plus, CVE-2026-123007 | R33 through R36 and affected 37.x releases | 37.0.8.1 or 37.3.0.137.0.8.1 or 37.3.0.1 |
For NGINX Plus, versions 37.0.8.1 and 37.3.0.1 address both vulnerabilities on their respective release tracks. Customers running older NGINX Plus branches should upgrade to a supported release containing the appropriate fixes.
Organizations using NGINX through operating system packages, container images or third party distributions should consult their provider’s security advisories for the applicable fixed versions, including any backported security updates.
How can organizations identify and remediate affected NGINX deployments?
Organizations should prioritize internet facing NGINX deployments and review both installed versions and HTTP/2 configurations to determine potential exposure.
Recommended actions include:
- Identify affected deployments. Review NGINX servers, container images, reverse proxies and Kubernetes ingress controllers to locate potentially vulnerable versions.
- Verify HTTP/2 configuration. Confirm whether HTTP/2 is enabled on affected services, since both vulnerabilities require HTTP/2 for exploitation.
- Apply available security updates. Upgrade to the appropriate patched NGINX release or follow the guidance provided by the operating system or product vendor.
- Consider temporary mitigation. If immediate patching is not possible, consider disabling HTTP/2 on affected listeners. Test application compatibility before making changes, 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 scanning results.
Organizations running F5 NGINX Ingress Controller should upgrade to version 5.8.0, while those using NGINX Gateway Fabric should upgrade to version 2.9.0.
The archived community Kubernetes ingress nginx project also includes vulnerable NGINX versions and has no planned security fix. Organizations using this project should review their HTTP/2 configurations and plan migration to a maintained alternative.
How does Aquasec help identify images affected by the NGINX vulnerabilities?
Aquasec has completed its assessment of CVE-2026-123633 and CVE-2026-123007 and confirmed that Aquasec products are not affected. No Aquasec product updates or remediation are required.
Detection for both vulnerabilities is now available in Aquasec’s Online and Offline CyberCenter vulnerability feeds.
Customers can rescan potentially affected NGINX container images and use Aquasec’s native vulnerability scanning and Image Assurance Policies to identify images with matching CVE findings.
Detection coverage may depend on the availability of vulnerability information from individual operating system and package vendors. An image without a CVE finding should not automatically be considered unaffected.
Customers should continue to verify their NGINX versions and HTTP/2 configurations against the applicable vendor advisories, even when vulnerability scanning does not report either CVE.
For detailed information on detection coverage and recommended actions, refer to the Aquasec Knowledge Base.
What should organizations do next?
The immediate priority is to identify affected NGINX deployments and apply the available security updates. Because both vulnerabilities could enable unauthenticated remote code execution, organizations should prioritize internet facing services and verify that patched versions are running in production.
Aquasec customers can use the updated Online and Offline CyberCenter vulnerability feeds to help identify potentially affected images, while continuing to validate NGINX configurations and vendor security guidance.
For additional technical details and remediation information, consult the official NGINX security advisories.
No. Aquasec has confirmed that its products are not affected by either vulnerability. No Aquasec product updates or remediation are required.
Yes. Detection for CVE-2026-123633 and CVE-2026-123007 is available in Aquasec’s Online and Offline CyberCenter vulnerability feeds. Customers can rescan container images to identify matching vulnerability findings.
Both vulnerabilities require HTTP/2 to be enabled. Disabling HTTP/2 on affected listeners can be considered as a temporary mitigation when immediate patching is not possible. Organizations should test application compatibility before making changes and apply the available security updates as the recommended remediation.
Potentially. Products that incorporate vulnerable NGINX versions may be affected. Organizations should review the versions used by their ingress controllers and follow the applicable vendor security guidance.
Not necessarily. Detection coverage depends on available vulnerability information from operating system and package vendors. Organizations should verify installed NGINX versions and HTTP/2 configurations even when no matching CVE finding appears.