CVE-2026-123634: NGINX resolver vulnerability

Published Nov 18, 2026
·
Updated

This issue occurs when NGINX Plus or NGINX Open Source is configured a ...

Affected Software

18 affected componentsFixes available
F5 NGINX Open Source
F5 NGINX Plus
F5 NGINX Plus>=37.1.0<=37.2.0.1, >=37.0.0<=37.0.7.1
37.3.0.137.0.8.1
F5 NGINX Plus=34
F5 NGINX Open Source>=1.31.0<=1.31.8, >=1.0.0<=1.30.6
1.31.91.30.7
F5 NGINX Open Source>=0.6.18<=0.8.55
debian/nginx*
debian/nginx*
debian/nginx*
debian/nginx<=1.22.1-9+deb12u9, <=1.22.1-9+deb12u10, <=1.26.3-3+deb13u7, <=1.26.3-3+deb13u10, <=1.30.6-3, <=1.30.6-4
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*
ubuntu/nginx*

Remediation

Recommended actions to resolve this vulnerability, in priority order.

  1. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 37.3.0.1Fixed in 37.0.8.1
  2. Upgrade

    Upgrade to a fixed release to a version that resolves this vulnerability.

    Fixed in 1.31.9Fixed in 1.30.7

Event History

Nov 18, 2026
Advisory Published
via F5·02:50 PM
Data Sourced
via F5·02:50 PM
DescriptionSeverityWeaknessAffected Software
CVE Published
via OSV·03:23 PM
Data Sourced
via OSV·03:23 PM
DescriptionSeverityAffected Software
CVE Published
via MITRE·03:23 PM
Data Sourced
via MITRE·03:23 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·04:18 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

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.

2

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.

3

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.

4

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.

Contact

SecAlerts Pty Ltd.
132 Wickham Terrace
Fortitude Valley,
QLD 4006, Australia
info@secalerts.co
By using SecAlerts services, you agree to our services end-user license agreement. This website is safeguarded by reCAPTCHA and governed by the Google Privacy Policy and Terms of Service. All names, logos, and brands of products are owned by their respective owners, and any usage of these names, logos, and brands for identification purposes only does not imply endorsement. If you possess any content that requires removal, please get in touch with us.
© 2026 SecAlerts Pty Ltd.
ABN: 70 645 966 203, ACN: 645 966 203