These affect Linux web servers and reverse proxies, which forward web traffic to other services.
By exploiting these vulnerabilities (referred to as NGINX2Root), arbitrary commands can be executed as an NGINX worker, the process handling web requests. By further exploiting a vulnerability within the Linux kernel, privilege escalation to root (administrator) on the host can be achieved. However, this may not be possible depending on the server.
As of November 19, the Western Australia Security Operations Center reports exploitation of at least one of the two HTTP/2 vulnerabilities. To mitigate risks in your systems, find which of your servers are vulnerable, apply the appropriate patch and confirm it is in place.
What Has Changed in the NGINX Update?
This update fixes the five NGINX vulnerabilities discussed here, along with other security vulnerabilities and bugs. These five vulnerabilities affect setups using HTTP/2, HTTP/3, specific DNS lookups and mail proxy. Each vulnerability requires different conditions to be in place.
The vulnerabilities have been patched in version 1.30.7 (stable) and 1.31.9 (mainline). Find out which supported version is relevant for your branch/vendor. It may not be necessary to change branches.
HTTP/2 contains two vulnerabilities. CVE-2026-123007 allows memory corruption through incorrect counting. CVE-2026-123633 can leave a request using memory that has already been freed.
Wizâs table compares the two HTTP/2 memory flaws that can allow attackers to run code without signing in.
Which NGINX Servers Are Affected?
If an attacker can reach your server, you are running a vulnerable version of NGINX and using vulnerable functionality, then you may be vulnerable. An unpatched server with the affected HTTP/2 feature enabled may be vulnerable to untrusted clients. Even static sites may be vulnerable.
According to Wiz (Nir Ohfeld and Tomer Schwartz), code execution vulnerabilities may exist in static content delivered via HTTP/2. Issues in back-end applications were not required. Like recent PHP vulnerabilities, vulnerabilities in server software could expose otherwise secure applications. The second HTTP/2 vulnerability affects reverse-proxy processing when available worker connection slots run low.
To check each flaw, review your serverâs configuration. Xint describes the following affected configurations.
- CVE-2026-123007: HTTP/2 is enabled on an unpatched server.
- CVE-2026-123633: HTTP/2 requests are sent to a backend server while available worker connection slots run low.
- CVE-2026-121810: HTTP/3 requests are sent to a backend server while available worker connection slots run low.
- CVE-2026-123634: Resolution of DNS during requests. A proxy destination is derived from the request, and a subrequest is performed for the same name. In testing, mirror requests with mirror_request_body off were vulnerable. Server-side includes may also be vulnerable.
- CVE-2026-113425: The mail proxy is enabled with proxy on and uses auth_http for authentication.
Each vulnerability is a different attack vector. Disabling HTTP/2 will not prevent exploitation of HTTP/3, DNS, or mail proxy. Disabling mirror configuration alone will not prevent exploitation of the DNS vulnerability.
Have Attackers Exploited NGINX2Root?
One or more of the vulnerabilities in HTTP/2 listed in the government advisory have been exploited in real-world scenarios, according to the Western Australia Security Operations Center. However, as of now, the team has received no reports of exploitation on Western Australian Government networks.
It is unknown which parties exploited these vulnerabilities, how many hosts were exploited, or if exploitation of the kernel vulnerability occurred. Prior advisories on November 18 did not mention any known exploitation.
Will Attackers Always Gain Root Access?
Not necessarily. Successful exploitation can allow attackers to run code with the NGINX workerâs permissions, which are normally restricted. To gain full access to the host, another route is needed, unless the NGINX worker has root access.
By chaining this vulnerability with a vulnerability in the Linux SCTP networking protocol code, root access on the host may be achieved. In testing, Xint was able to gain root access even when NGINX was running inside Docker. This depends on the kernel, modules and hardening in place on the host. Earlier SCTPhantom reporting also shows why SCTP availability matters to container exposure. That earlier report does not establish whether this new kernel issue is fixed.
Xintâs November 18, 2026 report described the kernel vulnerability as unpatched. Please ensure you follow the latest guidance from your kernel vendor. If SCTP is not required on the host, Xint recommends preventing the module from loading. If the module is already loaded or SCTP is statically compiled into the kernel, this will not prevent SCTP from being present.
How Can I Check My NGINX Build?
Type nginx -v to get the upstream version. Type nginx -V to get build options. If --with-http_v2_module is present, it confirms that HTTP/2 is supported in the binary. However, it does not confirm HTTP/2 is enabled, accessible, or unpatched.
Check the full version of the package you are running and compare with the advisory from your vendor. Also check the configuration of the active listener. If using a CDN, it is possible that the test traffic is hitting the proxy rather than the origin. None of these checks alone confirms that the patched version is handling live traffic.
How Do I Apply the NGINX Vulnerability Fix?
Ensure that you are running 1.30.7, 1.31.9, or updated versions from a supported vendor. Depending on the vendor, patches may be backported into older versions.
AlmaLinux backported these fixes into supported streams on November 18. These fixes were not added to retired streams. Check the full version of the package, and compare with the advisory from your supplier. A short NGINX version check does not confirm the patch has been applied.
AlmaLinux lists the patched NGINX package revisions for its supported releases and streams.
If NGINX is used in other products (hosting panels, appliances, container images, or cluster routing tools), updating NGINX on the host will not update NGINX in those products. If using NGINX Plus, please refer to F5.
Once updated, restart NGINX or use a supported method to replace the running program. Simply reloading the configuration will not do this. As detailed in the NGINX control documentation, old workers may be serving existing clients after a reload.
Can I Disable HTTP/2 Temporarily?
Yes. Disabling HTTP/2 on vulnerable listeners will prevent exploitation of the two HTTP/2 vulnerabilities. However, it will not prevent exploitation of the other vulnerabilities (HTTP/3, DNS and mail proxy). This is therefore only a temporary solution.
Refer to guidance for your version to disable HTTP/2. Confirm that HTTP/2 has been properly disabled, and no existing connections are using HTTP/2. If services require HTTP/2 (such as native gRPC), disabling HTTP/2 may cause issues. Consider how this may impact users. Other attacks on HTTP/2 may impact service availability.
What Should I Check After Updating?
Ensure that the service in use is protected. In the case of containers, ensure that the image has been patched. Ensure no traffic is being sent to unpatched instances. Ensure the image/template used to make new servers has been updated. Add this change to your deployment workflow so that in the next deployment, an old image is not deployed.
Record the current version of the package/image in use, which features of NGINX are in use, and evidence that the patched software is in use. This helps whoever comes after you understand changes that have been made and actions to take.
Investigate any unexpected termination of NGINX workers, unexpected commands executed in NGINX or changes on the host. Just because a worker has unexpectedly terminated does not mean that an attacker executed code. Likewise, a normal access log does not exclude this possibility. Save useful logs, and if exploitation is suspected, contact your incident response team.
More Questions About NGINX
Am I Safe With a CDN in Place?
Not necessarily. If you are performing public testing, traffic may be sent to the CDN. Check whether the origin can be reached directly, from other networks, and supported protocols.
Does Applying This Patch Mean My Server Was Never Compromised?
No. This patch closes these attack paths, but does not show whether the server was compromised before. If evidence of compromise exists, apply the patch to NGINX, and investigate the host and any exposed passwords, keys, or tokens.
Check the Server and Host
Ensure that the correct patch for the NGINX vulnerability has been applied to any NGINX processes that may be exploitable. Check the current software and whether there is a risk of exploitation of the kernel vulnerability. This applies to NGINX in containers or other products. Ensure that, on all servers, the updated (patched) version of NGINX is processing traffic.
For more original Linux security content, sign up for the LinuxSecurity newsletter.
Комментарии (0)
Пока нет комментариев — будьте первым.