CVE-2026-42945: CVE-2026-42945: NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module modul…

What it is

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_rewrite_module module. This vulnerability exists when the rewrite directive is followed by a rewrite, if, or set directive and an unnamed Perl-Compatible Regular Expression (PCRE) capture (for example, $1, $2) with a replacement string that includes a question mark (?). An unauthenticated attacker along with conditions beyond its 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.

Exploitation evidence

First exploit evidence seen: 2026-05-14 (earliest date across the sources below).

Exploited in the wild

No source on this site lists in-the-wild exploitation yet (CISA KEV, VulnCheck KEV).

Public exploit code

GitHub proof-of-concept repositories

46 public repositories from 46 accounts, first seen 2026-05-14. Most starred: cipherspy/CVE-2026-42945-POC (64 stars), view repository.

Verify before running: public PoCs can be malicious. Read the code and only run it in an isolated lab. A PoC means exploit code is public, not that this CVE is exploited in the wild.

Sources: nomi-sec/PoC-in-GitHub.

How to fix it

Fixed versions

• f5 dos: versions up to and including 4.7.0 are affected; check the vendor advisory for the fixed release.
• f5 nginx gateway fabric: versions up to and including 1.6.2 are affected; check the vendor advisory for the fixed release.
• f5 nginx gateway fabric: versions up to and including 2.5.1 are affected; check the vendor advisory for the fixed release.
• f5 nginx ingress controller: versions up to and including 3.7.2 are affected; check the vendor advisory for the fixed release.
• f5 nginx ingress controller: versions up to and including 4.0.1 are affected; check the vendor advisory for the fixed release.
• f5 nginx ingress controller: versions up to and including 5.4.1 are affected; check the vendor advisory for the fixed release.
• f5 nginx instance manager: versions up to and including 2.21.1 are affected; check the vendor advisory for the fixed release.
• f5 nginx open source: versions up to and including 1.30.0 are affected; check the vendor advisory for the fixed release.
• f5 nginx plus: versions up to and including r36 are affected; check the vendor advisory for the fixed release.
• f5 waf: versions up to and including 4.16.0 are affected; check the vendor advisory for the fixed release.
• f5 waf: versions up to and including 5.8.0 are affected; check the vendor advisory for the fixed release.
• f5 waf: versions up to and including 5.12.1 are affected; check the vendor advisory for the fixed release.

Derived from the NVD CPE configuration (versionEndExcluding / versionEndIncluding). Always confirm with the vendor advisory.

Vendor advisories and patches

• https://my.f5.com/manage/s/article/K000161019 (Mitigation, Vendor Advisory)
• https://depthfirst.com/nginx-rift (Mitigation, Technical Description, Third Party Advisory)

MITRE ATT&CK mitigations for this chain

• M1048 Application Isolation and Sandboxing (for T1190, T1203) : Application isolation will limit what other processes and system features the exploited target can access.
• M1037 Filter Network Traffic (for T1190) : Restrict outbound network traffic from public-facing servers to prevent unauthorized connections from initiating communications with attacker-controlled infrastructure. While this may not prevent the initial exploitation, it limits the attacker's ability to verify and control the compromised server post-exploit, reduci
• M1030 Network Segmentation (for T1190) : Segment externally facing servers and services from the rest of the network with a DMZ or on separate hosting infrastructure.
• M1016 Vulnerability Scanning (for T1190) : Regularly scan externally facing systems for vulnerabilities and establish procedures to rapidly patch systems when critical vulnerabilities are discovered through scanning and through public disclosure.
• M1026 Privileged Account Management (for T1190) : Use least privilege for service accounts will limit what permissions the exploited process gets on the rest of the system.
• M1050 Exploit Protection (for T1190, T1203) : Web Application Firewalls may be used to limit exposure of applications to prevent exploit traffic from reaching the application.
• M1035 Limit Access to Resource Over Network (for T1190) : Ensure that all publicly exposed services are actually intended to be so, and restrict access to any that should only be available internally.
• M1051 Update Software (for T1190, T1203) : Update software regularly by employing patch management for externally exposed applications.

Detection Generic guidance

• Initial Access: Alert on unusual requests to the affected service (odd paths, oversized payloads, exploit strings) in WAF, reverse-proxy and application logs.
• Execution: Watch for the service process spawning shells or script interpreters (cmd.exe, powershell, sh, bash, python) via EDR process-tree rules.

Response checklist Generic guidance

1. Inventory: find every instance of the affected product and version (include internet-facing and forgotten ones).
2. Patch or mitigate per the vendor advisory; if you cannot patch, remove internet exposure or apply the vendor workaround.
3. Assume compromise if the system was exposed before patching: hunt for the indicators in the advisory and review logs back to the disclosure date.
4. Rotate credentials and secrets stored on or used by the affected system if compromise cannot be ruled out.