NGINX administrators should check their internet-facing servers after fixes released November 18 addressed two HTTP/2 vulnerabilities that can allow remote code execution without a login. The fixes are available in NGINX Open Source 1.30.7 and 1.31.9, alongside patches for other security flaws.
The two HTTP/2 issues, CVE-2026-123007 and CVE-2026-123633, have different prerequisites. Turning off HTTP/2 on exposed listeners can temporarily mitigate both, but it does not address the other vulnerabilities in the release. Updating the relevant package or image remains the priority.
Researchers have demonstrated exploitation, and public proof-of-concept code exists for CVE-2026-123007. CERT-EU’s advisory reports no known exploitation in the wild as of its publication. A proof of concept is not the same as evidence that attackers have compromised production systems.
Which NGINX servers are exposed?
CVE-2026-123007 affects HTTP/2 flow control and can corrupt memory when HTTP/2 is enabled on a listening port. The second issue, CVE-2026-123633, is a use-after-free affecting configurations that both accept HTTP/2 and proxy requests to an upstream server under connection-draining conditions.
According to the NGINX security advisories, upstream versions 1.9.5 through 1.31.8 are vulnerable to the first flaw, and versions 1.19.7 through 1.31.8 to the second. Fixed upstream releases are 1.30.7 and 1.31.9. Distribution packages can carry backported fixes without changing the upstream version number, so check the package vendor’s advisory rather than relying on the version banner alone.
Inventory reverse proxies, ingress controllers, appliance software and container images as well as standalone servers. The NGINX binary serving traffic may be bundled inside another product or image, and an update to the host alone may not replace it.
Check configuration and patch the running service
- Run
nginx -vto identify the installed version andnginx -Vto inspect build options. Runnginx -Twith appropriate privileges to display the effective configuration, including included files. Its output may contain sensitive configuration details, so handle it accordingly. - Find exposed HTTP/2 listeners and identify which services proxy to upstream applications. Also check HTTP/3, DNS resolver and mail proxy configurations: other flaws in this release have different prerequisites.
- Install a fixed upstream release or the corrected package from your operating-system or product vendor. For NGINX Plus, follow the applicable vendor advisory for your release; do not assume the open-source version numbers map directly to Plus.
- Rebuild and redeploy affected container images or update managed products through their supported process. Test the configuration with
nginx -t, then restart or replace running instances according to your deployment procedure. Confirm that the new binary is actually serving traffic.
Prioritize externally reachable systems, while testing changes against a representative workload. A package installation or a configuration reload alone is not proof that every running worker or container has been replaced.
What to do while waiting for a fix
If a fixed build is not yet available, CERT-EU recommends disabling HTTP/2 on exposed listeners to mitigate the two HTTP/2 vulnerabilities. Depending on the NGINX version and configuration, that means removing the http2 parameter from listen directives or setting http2 off;. Validate the configuration before applying it and test clients and applications that depend on HTTP/2. Restricting access to affected listeners can further reduce exposure.
This is a temporary measure, not a complete fix. The same disclosure includes an HTTP/3 issue and separate resolver and mail proxy flaws that require their own configurations. Disabling HTTP/2 does not resolve those paths; use the full advisory and your vendor’s guidance to assess them.
Does the flaw automatically give attackers root?
No. The NGINX flaws can allow code execution with the privileges of an NGINX worker process. Research group Xint demonstrated a chain that combines an NGINX vulnerability with a separate Linux kernel SCTP flaw to reach host root, including from a container. That demonstration is a warning about chained weaknesses, not a claim that every vulnerable NGINX installation directly grants root.
Review operating-system kernel updates and vendor guidance alongside the NGINX remediation. Preserve logs and investigate suspicious activity under your normal incident-response procedures; installing a fix does not by itself establish whether a server was previously compromised.