CVE-2026-42533: Heap Buffer Overflow in NGINX Regex Map Variable Evaluation
- Vendor
- F5
CVE-2026-42533 is a heap-based buffer overflow in the internal script engine of NGINX Open Source and NGINX Plus. The engine constructs variable-containing strings using separate length-calculation and copying passes. Evaluating a regex-based map can change regex capture state between these passes, causing more data to be copied than the allocated buffer can hold. A vulnerable configuration references the map's regex capture variables before its output variable in a string expression; certain uses of non-cacheable variables can also trigger the flaw. Unauthenticated attackers can send crafted requests to corrupt an NGINX worker's heap, causing a worker restart or potentially arbitrary code execution. Vulnerable Stream configurations using TLS preread can also expose the affected evaluation path. The vulnerability affects the data plane only, with no control-plane exposure.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Remote exploitation can crash or restart NGINX worker processes, disrupting request processing and causing denial of service. Repeated triggering can sustain service disruption. Arbitrary code execution is possible when Address Space Layout Randomization (ASLR) is disabled or successfully bypassed, potentially compromising the confidentiality and integrity of data accessible to the worker process. Enabling ASLR does not eliminate the underlying overflow or denial-of-service risk.
Mitigation
If you can’t patch tonight, do this now.
Replace unnamed regex captures with unique named captures, reference them only within the block containing the regex match, and do not reuse capture names across regex matches in different directives. Review complex expressions to avoid capture references before map output variables and remove problematic non-cacheable-variable evaluation patterns where feasible. Named captures alone are not a complete substitute for updating. Restrict untrusted access to affected HTTP and Stream listeners, particularly TLS-preread listeners. Keep ASLR enabled to reduce code-execution risk, while recognizing that it neither prevents worker crashes nor guarantees protection against exploitation.
Remediation
Patch, then assume compromise.
Install a current vendor-supported release containing the fix. Initial fixed releases include NGINX Open Source 1.30.4 and 1.31.3; NGINX Plus 37.0.3.1 or R36 P7; NGINX Instance Manager 2.22.2; F5 WAF for NGINX 5.13.4; NGINX Gateway Fabric 2.6.7; and NGINX Ingress Controller 2026-lts-r4 or 5.5.3. Prefer newer security-maintained releases: the original correction introduced the separately tracked regression CVE-2026-93479, addressed in NGINX 1.30.6 and 1.31.7. For distribution packages, install the latest applicable security update rather than relying solely on the upstream version number; some backports were reverted or subsequently corrected. Restart NGINX after updating to load the corrected binary and validate the configuration and request handling.
Exploits
6 exploits validated by Mallory's analysis. Hidden: 10 rejected by Mallory's analysis as not a working exploit.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-42533 exploited in the wild?
- Yes. As of Nov 14, 2026, Mallory has reports of exploitation in the wild.
- Is there a public exploit for CVE-2026-42533?
- Yes. Mallory tracks 6 public exploits or proofs of concept for CVE-2026-42533, the earliest disclosed Jul 27, 2026.
- Is there a patch for CVE-2026-42533?
- Install a current vendor-supported release containing the fix. Initial fixed releases include NGINX Open Source 1.30.4 and 1.31.3; NGINX Plus 37.0.3.1 or R36 P7; NGINX Instance Manager 2.22.2; F5 WAF for NGINX 5.13.4; NGINX Gateway Fabric 2.6.7; and NGINX Ingress Controller 2026-lts-r4 or 5.5.3.
- What products are affected by CVE-2026-42533?
- F5 Nginx Plus, F5 Nginx Gateway Fabric, F5 Nginx Ingress Controller, and F5 Waf.
- How severe is CVE-2026-42533?
- CVE-2026-42533 has a CVSS v4 score of 9.2 (Critical) and an EPSS score of 6.3% (94th percentile) as of Nov 14, 2026.
Recent activity
206 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.