Summary
- NGINX released stable version 1.30.7 and mainline version 1.31.9 on 18 November.
- Ten vulnerabilities were addressed, including HTTP/2, HTTP/3, resolver, mail proxy, and TLS-related issues.
- CERT-EU highlighted five potential remote code execution vulnerabilities and recommended prioritising exposed systems.
Organisations running NGINX web infrastructure face a substantial security update after maintainers released fixes for ten vulnerabilities, including memory corruption flaws with potential consequences for internet-facing services.
NGINX released stable version 1.30.7 and mainline version 1.31.9 on 18 November 2026. The updates address weaknesses affecting HTTP/2, HTTP/3, DNS resolution, proxy processing, and other components used to manage network traffic.
CERT-EU issued a separate advisory highlighting five vulnerabilities that could allow an unauthenticated remote attacker to execute code with the privileges of an affected NGINX worker process. It recommended prompt updates, particularly for systems accessible from the internet.
The vulnerabilities have different technical prerequisites and consequences. They should not all be described as remotely exploitable code execution flaws, nor does every NGINX installation necessarily use every affected feature.
Network processing weaknesses affect multiple components
NGINX is widely deployed as a web server, reverse proxy, and traffic management component. Its position between users and backend services makes it an important part of enterprise application infrastructure.
The November release includes CVE-2026-123007, a memory corruption vulnerability involving HTTP/2 flow control, alongside separate use-after-free vulnerabilities affecting HTTP/2, HTTP/3, and resolver processing.
A use-after-free condition occurs when software continues to access memory after it has been released. Depending on the surrounding application logic, such weaknesses can lead to crashes, unintended behaviour, or more serious exploitation.
Other corrected issues include an infinite loop while reading request bodies over TLS 1.3, a mail proxy vulnerability, a null pointer dereference involving PROXY protocol version 2, and a buffer overflow associated with particular file handling configuration.
The updates also address a server name indication bypass involving client certificate validation in the stream module and insufficient validation within stream SSL preread handling.
These vulnerabilities differ in severity, affected versions, and required configurations. For example, exposure associated with HTTP/3 processing depends on whether the relevant functionality is present and enabled, while a mail proxy weakness is not equivalent to one affecting ordinary HTTP request handling.
NGINX’s official security advisories identify fixed releases for each issue. Version 1.30.7 provides the stable-branch corrections, while version 1.31.9 addresses the relevant vulnerabilities in the mainline branch.
Reverse proxies concentrate application dependencies
Many organisations place NGINX in front of customer portals, identity systems, application programming interfaces, and internal services. It may handle encrypted connections, route requests, and apply controls before traffic reaches the underlying application.
That position makes the security of the proxy consequential even when the application behind it is fully patched. If an attacker compromises the traffic-handling layer, access to requests or connected services may be possible within the permissions available to the affected process.
Execution as an NGINX worker does not automatically establish unrestricted administrative control of a host. The consequences depend on process privileges, operating system protections, network segmentation, and access to backend resources.
Deployments also vary. Organisations may run NGINX directly on servers, inside containers, or as part of a commercial application or managed hosting environment. The software version recorded in a central inventory may not always describe the binary actually processing production traffic.
Commercially supported NGINX Plus installations require review of their corresponding vendor advisories and supported fixes. Open-source release numbers should not automatically be treated as the correct remediation targets for every packaged product.
Patching must account for production availability
Because web servers and reverse proxies support live applications, updates require coordination with operational teams. Administrators may need to test configuration compatibility and confirm that corrected binaries are running after deployment.
Where servers operate in clusters, maintenance can sometimes be sequenced to preserve service availability. However, the appropriate approach depends on traffic architecture, capacity, session handling, and the organisation’s established change procedures.
CERT-EU’s advisory prioritises internet-facing systems because they may receive untrusted traffic without an intermediate control capable of restricting the vulnerable interaction.
Configuration changes can reduce exposure to particular weaknesses, but a mitigation for one protocol or module should not be assumed to address unrelated issues elsewhere in the release.
Administrators also need to examine externally supplied NGINX builds, including those embedded in appliances or distributed through operating system packages. Vendors may incorporate fixes while retaining their own package versioning conventions, making direct version comparisons unreliable without the supplier’s advisory.
At the time of CERT-EU’s advisory, exploitation in the wild had not been publicly confirmed. The absence of a reported campaign does not change the need to assess systems affected by serious flaws in widely deployed network infrastructure.
The November releases provide corrected versions for NGINX Open Source. Organisations relying on the software through other products or deployment models must establish which fixes apply and confirm that production services have been updated accordingly.





