CVE-2026-42533: NGINX Map directive and Regex matching vulnerability
A vulnerability exists in NGINX Plus and NGINX Open Source when a map directive uses regex matching and a string expression 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.
Other sources
NGINX Map directive and Regex matching vulnerability
— Microsoft
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 1.28.3-8
Event History
Frequently Asked Questions
What is the severity of CVE-2026-42533?
CVE-2026-42533 has a severity rating of 8.1, categorized as high.
How do I fix CVE-2026-42533?
To fix CVE-2026-42533, update your NGINX Plus or NGINX Open Source to the latest version that addresses this vulnerability.
What systems are affected by CVE-2026-42533?
CVE-2026-42533 affects both NGINX Plus and NGINX Open Source deployments using the map directive with regex matching.
What type of vulnerability is CVE-2026-42533?
CVE-2026-42533 is classified as a Buffer Overflow vulnerability.
What mitigation strategies can be employed for CVE-2026-42533?
Mitigation strategies for CVE-2026-42533 include avoiding the use of regex capture variables in association with the map output variable or ensuring variable cacheability.