NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module module. This vulnerability exists when a rewrite directive uses a regex pattern with distinct, overlapping Perl-Compatible Regular Expression (PCRE) captures (for example, ^/((.*))$) and a replacement string that references multiple such captures (for example, $1$2) in a redirect or arguments context. 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.
Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Security readout for executives and security teams
Plain-English summary
A specially crafted web request can crash an NGINX worker when a vulnerable rewrite rule combines overlapping regex captures and reuses multiple captures. Under less common conditions—ASLR disabled or bypassed—the flaw may permit code execution. Internet-facing systems with matching configurations deserve urgent review, although exploitation requires specific conditions.
Executive priority
Treat as an urgent, targeted remediation. Immediately identify internet-facing NGINX systems, then prioritize those with the vulnerable rewrite pattern. The 9.2 score and potential code execution justify rapid action, while the configuration and ASLR preconditions make indiscriminate emergency shutdowns unwarranted.
Technical view
CVE-2026-9256 is a CWE-122 heap buffer overflow in ngx_http_rewrite_module. It requires distinct, overlapping PCRE captures and a replacement referencing multiple captures in a redirect or arguments context. Unauthenticated crafted requests can restart a worker; code execution additionally requires disabled or bypassed ASLR. CVSS 4.0 is 9.2.
Likely exposure
Exposure is configuration-dependent, not established by product presence alone. Prioritize internet-facing NGINX Plus and NGINX Open Source instances using rewrite directives with overlapping captures and multiple capture references. The supplied version data is ambiguous, so confirm applicability through F5 or operating-system vendor guidance.
Exploitation context
The bundle does not establish active exploitation, and the CVE is not listed as KEV. Network access and no authentication are required, but attack complexity is high and additional conditions apply. Worker crashes are the clearest expected impact; code execution depends on ASLR being disabled or bypassed.
Researcher notes
The vulnerable path requires overlapping PCRE captures, multiple capture substitutions, and redirect or arguments processing. The public bundle does not provide exploit telemetry or explicit fixed-version details. Avoid inferring exposure solely from the listed versions; validate configuration reachability, package provenance, ASLR posture, and vendor applicability.
Mitigation direction
Review F5 advisory K000161377 for applicable fixed releases and configuration guidance.
Apply relevant F5 or operating-system vendor security updates after testing.
Replace affected rewrite expressions with non-overlapping capture patterns where operationally feasible.
Keep ASLR enabled as defense-in-depth; it does not eliminate the crash risk.
Restrict unnecessary public access until exposed instances are assessed and remediated.
Validation and detection
Inventory NGINX Plus and NGINX Open Source versions on all reachable systems.
Search configurations for rewrite directives containing nested or overlapping PCRE capture groups.
Identify replacements referencing multiple captures in redirect or arguments contexts.
Confirm installed packages against F5, Debian, or Red Hat advisories.
Verify ASLR is enabled and investigate unexplained NGINX worker restarts.
Retest configuration behavior and service stability after remediation.
Generated from the cited source records. This long-tail analysis has not been individually reviewed by a named human.
Potential ATT&CK relevance
Conservative CVE-to-ATT&CK context
These mappings and lookup hints may be relevant to the vulnerability behavior, CWE, affected product, or exposure path. Glexia-inferred context is not an official MITRE, ATT&CK, CWE, or CVE Program mapping.
ATT&CK lookup starting points
Use these exact CWE pages and searches to review the Glexia ATT&CK library from this CVE's weakness and description context.
cwe · low confidence lookup
CWE-122: Exact CWE lookup
Use the exact CWE identifier as the starting point before reviewing related ATT&CK behavior. Open the exact CWE lookup page first, then review the ATT&CK searches from that MITRE weakness context. This is a Glexia lookup hint, not an official ATT&CK mapping.
These fields come from the CVE record and ADP containers, not from Glexia's Take. They preserve time-varying source decisions such as CISA SSVC, KEV status, CVSS metrics, and provider references.
3CVSS vectors
5Timeline events
3ADP providers
15Source links
SSVC decision data
CISA-ADPCISA Coordinator
Timestamp
Version
2.0.3
Exploitation: noneAutomatable: noTechnical Impact: total
CVSS vector scores
3 official scores
We collect every scored CVSS vector available in the official CNA and ADP containers. When more than one version is present, the table keeps the source vectors side by side instead of collapsing them into the highest score.
CWE links open Glexia weakness intelligence pages with official CWE context, developer remediation guidance, and related CVE mappings.
CWE-122 · source CWE mapping
Heap-based Buffer Overflow
Heap-based Buffer Overflow represents a recurring weakness pattern that can create exploitable paths when design, validation, or implementation controls are missing.