// 1 ZERO-DAY · 2 CVE · 2 EXPLOIT IN THE LAST 24H→
A heap buffer overflow in NGINX's two-pass scripting engine puts 15 years of releases at risk. The patch landed July 15, 2026; F5 conditions RCE on disabled or bypassed ASLR, while an independent researcher claims the same flaw enables bypass on default systems.

F5 patched a critical vulnerability in the NGINX scripting engine on July 15, 2026. The flaw, CVE-2026-42533, dates to 2011 and affects fifteen years of open-source and commercial releases. The two-pass engine that handles regex maps overwrites its own capture state between the measurement and write phases, resulting in a heap buffer overflow. F5 conditions remote code execution on ASLR being disabled or bypassed; an independent researcher argues the same flaw permits bypass on default systems.

Key Takeaways
  • The vulnerability affects NGINX from version 0.9.6 (2011) through 1.31.2, spanning fifteen years of releases.
  • The mechanism exploits the overwrite of regex capture state between the measurement and write phases of the two-pass engine.
  • F5 conditions RCE on ASLR being disabled or bypassed; researcher Stan Shaw contends the flaw itself enables bypass on Ubuntu 24.04, a claim not independently verified.
  • The interim mitigation using named captures leaves a second exploitation path open, according to Shaw.

The Two-Pass Engine: How the Flaw Works

The defect lies in how NGINX processes string expressions involving map directives with regex matching. The engine operates in two phases: first it measures the memory needed and allocates a buffer, then it writes the actual content. Between the two phases, evaluation of the map's regex overwrites the original capture state that the first pass used to calculate the size. The second pass then writes attacker-controllable data of arbitrary length into a buffer of the wrong size.

According to the official CVE record, the vulnerable string must reference the map's regex capture variables before referencing the map's output variable itself. This specific sequence is the trigger that executes the state overwrite between the two passes. The condition is configurational: it requires a regex map whose output is used in a subsequent string expression after a numbered capture from a prior regex.

The National Vulnerability Database classifies the flaw as CWE-122 (heap buffer overflow) with a CVSS v3.1 score of 8.1 (HIGH) and a CVSS v4.0 score of 9.2 (CRITICAL). The attack vector is network-based, requires no privileges or user interaction, but attack complexity is high due to the need to reach the trigger configuration.

Conditional RCE and the ASLR Debate

In its July 15 advisory, F5 Networks scopes the maximum impact: remote code execution is possible on systems with ASLR disabled or when an attacker can bypass it. Absent those conditions, the documented impact is a crash and cyclic restart of worker processes — a denial of service.

Stan Shaw, an independent researcher known as cyberstan, disputes this reading. As reported to The Hacker News, the oversized buffer returns uninitialized heap data, and on a default Ubuntu 24.04 build a single unauthenticated GET request retrieves the addresses needed for an ASLR bypass payload. Shaw reported a 100% success rate in his own tests — as stated by the researcher, not independently verified.

"A reader of the F5 advisory could reasonably conclude this is DoS-only on default systems. It is not" — Stan Shaw (cyberstan)

Shaw also verified with AddressSanitizer that the interim mitigation recommended by F5 — replacing numbered captures with named captures — leaves a second path open through which a map defining the same named group as the location regex reaches the same overflow.

Vulnerable Versions and Patches

The vulnerable version range is exceptionally broad: from 0.9.6 in 2011, when the map directive gained regex support, through 1.31.2. The patches released July 15 are version 1.30.4 for the stable branch, 1.31.3 for the mainline branch, and release 37.0.3.1 for NGINX Plus.

F5 confirmed the vulnerability also affects NGINX Ingress Controller, NGINX Gateway Fabric, NGINX App Protect WAF, and NGINX Instance Manager.

Reporting of the flaw resulted from a rare convergence: more than a dozen researchers reported the issue independently, and CVE.org lists fourteen names in the official credits. No public exploit code is available as of July 20, 2026. Shaw has announced plans to publish a proof-of-concept 21 days post-patch, approximately August 5, 2026.

What to Do Now

  • Upgrade immediately to NGINX 1.30.4, 1.31.3, or NGINX Plus 37.0.3.1: these are the only versions that fully close the flaw, per Shaw.
  • Check for map configurations with regex whose output is referenced in string expressions after numbered captures from prior regexes: this is the documented trigger condition.
  • \li>Assess that the named-capture mitigation does not close all exploitation paths, per the researcher's verification.
  • Monitor for the PoC release slated for August 2026 to gauge concrete exposure.

Source Limitations and Editorial Notes

This analysis relies primarily on the F5 advisory via The Hacker News, with structural data from NVD and CVE.org. The advanced technical claims by Stan Shaw — including the ASLR bypass on Ubuntu 24.04 and the 100% success rate — have not been independently verified.

The source does not specify whether patched builds for NGINX Ingress Controller, Gateway Fabric, App Protect WAF, and Instance Manager are available. The source does not confirm whether exploitation in the wild has been observed: as of July 20, 2026, the CVE does not appear in the CISA KEV catalog.


Sources

Sources and references
  1. thehackernews.com
  2. nvd.nist.gov
  3. cve.org
  4. socprime.com
  5. cvemon.intruder.io
  6. cybernews.com
  7. bleepingcomputer.com
  8. techtimes.com