CVE-2026-93479: NGINX map directive and regex matching vulnerability

Published Oct 14, 2026
·
Updated

A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and the root directive or access log format references the map's regex capture variables before referencing the map output variable. Alternatively, the same result could be achieved by using a non-cacheable variable in a string expression under certain conditions. An unauthenticated attacker along with conditions beyond their control can exploit this vulnerability by sending crafted HTTP requests. This may cause a heap buffer overflow in the NGINX worker process leading to a restart. Additionally, attackers can execute code on systems with Address Space Layout Randomization (ASLR) disabled or when the attacker can bypass ASLR.

Impact:  This vulnerability may allow remote attackers to cause a denial-of-service (DoS) on the NGINX system or to possibly trigger a code execution. There is no control plane exposure; this is a data plane issue only.

Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Affected Software

2 affected components
Nginx NGINX Plus
Nginx NGINX Open Source

Event History

Oct 14, 2026
CVE Published
via MITRE·02:40 PM
Data Sourced
via MITRE·02:40 PM
DescriptionSeverityWeakness

Frequently Asked Questions

1

Which deployments are exposed?

NGINX Plus and NGINX Open Source deployments are affected when a map directive uses regex matching and the root directive or access-log format references the map regex capture variables before the map output variable. The issue can also occur when a non-cacheable variable is used in a string expression under certain conditions.

2

Does exploitation require authentication or control-plane access?

No authentication or control-plane access is required. This is a data-plane issue that can be triggered through crafted HTTP requests, although exploitation also depends on conditions beyond the attacker's control.

3

What is the likely impact if exploitation succeeds?

The overflow can cause the NGINX worker process to restart, resulting in denial of service. Code execution may also be possible where ASLR is disabled or the attacker can bypass ASLR.

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