CVE-2026-42533: NGINX Map directive and Regex matching vulnerability

Published Jul 15, 2026
·
Updated

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

23 affected componentsFixes available
Nginx NGINX Plus
Nginx NGINX Open Source
debian/nginx<=1.18.0-6.1+deb11u3, <=1.18.0-6.1+deb11u8, <=1.22.1-9+deb12u9, <=1.26.3-3+deb13u7, <=1.30.1-7
Microsoft azl3 nginx 1.28.3-6<1.28.3-8
1.28.3-8
F5 NGINX Gateway Fabric>=1.3.0<=1.6.2
F5 NGINX Gateway Fabric>=2.0.0<2.6.7
F5 NGINX Ingress Controller>=3.5.0<=3.7.2
F5 NGINX Ingress Controller>=5.0.0<5.5.3
F5 NGINX Ingress Controller>=2026-lts-r1<2026-lts-r4
F5 NGINX Ingress Controller=4.0.0
F5 NGINX Ingress Controller=4.0.1
F5 NGINX Plus>=37.0.0.1<37.0.3.1
F5 NGINX Plus>=r33<r36
F5 NGINX Plus=r36
F5 NGINX Plus=r36-p1
F5 NGINX Plus=r36-p2
F5 NGINX Plus=r36-p3
F5 NGINX Plus=r36-p4
F5 NGINX Plus=r36-p5
F5 NGINX Plus=r36-p6
F5 Waf Nginx>=4.11.0<=4.16.0
F5 Waf Nginx>=5.2.0<=5.8.0
F5 Waf Nginx>=5.9.0<5.13.4

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 1.28.3-8

Event History

Jul 15, 2026
CVE Published
via MITRE·02:33 PM
Data Sourced
via MITRE·02:33 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
DescriptionSeverityWeakness
Data Sourced
via NVD·03:16 PM
Affected Software
Jul 19, 2026
Data Sourced
via Microsoft·08:02 AM
DescriptionSeverityWeaknessAffected Software
Updated
via Microsoft·08:02 AM
DescriptionSeverity
Jul 20, 2026
Data Sourced
via Launchpad·06:10 PM
Description
Jul 21, 2026
Data Sourced
via Ubuntu·06:10 PM
RemedyDescriptionSeverityAffected Software
Data Sourced
via Debian·06:11 PM
DescriptionAffected Software
Free Weekly Intel

Don't miss critical vulnerabilities

Join thousands of security professionals who receive our weekly digest of trending CVEs, zero-days, and exploited vulnerabilities.

No spam. Unsubscribe anytime.

Frequently Asked Questions

1

What is the severity of CVE-2026-42533?

CVE-2026-42533 has a severity rating of 8.1, categorized as high.

2

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.

3

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.

4

What type of vulnerability is CVE-2026-42533?

CVE-2026-42533 is classified as a Buffer Overflow vulnerability.

5

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.

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