CVE-2026-123634: NGINX resolver vulnerability
This issue occurs when NGINX Plus or NGINX Open Source is configured a ...
Affected Software
Remediation
Recommended actions to resolve this vulnerability, in priority order.
- Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 37.3.0.1Fixed in 37.0.8.1 - Upgrade
Upgrade to a fixed release to a version that resolves this vulnerability.
Fixed in 1.31.9Fixed in 1.30.7
Event History
Frequently Asked Questions
Which deployments are exposed to this issue?
Affected deployments are NGINX Plus or NGINX Open Source instances configured as a proxy where the proxied server name contains variables. The configuration must also use SSI or a mirror directive to send a subrequest to a location that resolves that same server name.
What must an attacker do to trigger the vulnerability?
An attacker must send a specially crafted HTTP request to a deployment meeting the required proxy and subrequest configuration conditions. The supplied vector indicates no privileges or user interaction are required, although exploitation has high attack complexity.
What is the likely impact if exploitation succeeds?
Successful exploitation can crash an NGINX worker process or corrupt its memory. Remote code execution may also be possible when ASLR is disabled or can be bypassed by the attacker.
How can I determine whether my configuration is within the affected scenario?
Review proxy configuration for proxied server names that include variables, then identify SSI or mirror directives that generate subrequests. The described condition applies when those subrequests reach a location that resolves the same proxied server name.