1 technique observed across 1 entry about this entity, derived from entry metadata and body evidence, never asserted without a published entry behind it · pinned to MITRE ATT&CK v20.1 · compare on the matrix · Navigator layer (JSON)
Initial AccessExploit Public-Facing Application
Initial Access TA0001
T1190Exploit Public-Facing Application×1
Adversaries may attempt to exploit a weakness in an Internet-facing host or system to initially access a network. The weakness in the system can be a software bug, a temporary glitch, or a misconfiguration.
CVE-2026-42945 (CVSS 4.0: 9.2, codename "NGINX Rift") is a heap buffer overflow present in src/http/ngx_http_script.c since NGINX 0.6.27 (2008) (depthfirst "NGINX Rift" technical writeup, 2026-05-13 · NCSC-CH Security Hub #12575, 2026-05-15). The root cause: when a rewrite directive combines an unnamed PCRE capture ($1, $2) with a replacement string containing ?, followed by another rewrite, if, or set directive in the same scope, ngx_http_script_start_args_code() sets a flag causing the write phase to URI-encode URI argument characters (expanding escapable characters such as + and & from one byte to three), while the length-calculation phase computed a shorter buffer without this escaping. The result is a deterministic out-of-bounds write into the adjacent heap allocation. F5 says the flaw may cause a heap buffer overflow in the NGINX worker process leading to a restart (ENISA EUVD, 2026-09-10). depthfirst's proof of concept achieves code execution with ASLR off, and depthfirst notes that forked workers share one heap layout, which could in theory be used to leak ASLR (depthfirst, 2026-05-13); F5's CVE description, updated on 2026-09-10, covers systems with ASLR disabled or where the attacker can bypass ASLR (ENISA EUVD, 2026-09-10). A working PoC is public at github.com/depthfirstdisclosures/nginx-rift. depthfirst's internal analysis system found the flaw on 2026-04-18; depthfirst reported it to NGINX on 2026-04-21, shared its RCE proof of concept on 2026-05-05, and F5 released the advisory on 2026-05-13 (depthfirst, 2026-05-13). NCSC-CH rated the exploitation status "UNKNOWN, Proof of Concept Available" on 2026-05-15 (NCSC-CH Security Hub #12575, 2026-05-15); VulnCheck's honeypot reports followed two days later (below). Temporary workaround: replace all unnamed captures with named captures (e.g., (?<user_id>...) → $user_id) in rewrite directives, which eliminates the vulnerable code path without requiring upgrade. Affected: NGINX Open Source 0.6.27 to 1.30.0 (nginx.org); NGINX Plus R32 to R36; Ingress Controller 3.5.0 to 3.7.2, 4.0.0 to 4.0.1 and 5.0.0 to 5.4.1; Gateway Fabric 1.3.0 to 1.6.2 and 2.0.0 to 2.5.1; Instance Manager 2.16.0 to 2.21.1; F5 WAF for NGINX 5.9.0 to 5.12.1; App Protect WAF 4.9.0 to 4.16.0 and 5.1.0 to 5.8.0; F5 DoS for NGINX 4.8.0; App Protect DoS 4.3.0 to 4.7.0 (Security Affairs, 2026-05). Fixed: NGINX Open Source 1.30.1 and 1.31.0 (nginx.org); NGINX Plus R32 P6 and R36 P4 (Security Affairs, 2026-05).
VulnCheck reported exploitation attempts against its honeypot networks; the nature of the activity and its goals are unknown (The Hacker News, 2026-05-17).
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 (?).
The latest findings from VulnCheck show that threat actors have begun to weaponize the flaw, with exploitation attempts detected against its honeypot networks.
depthfirst reported the flaw to NGINX on 2026-04-21 and shared its code-execution proof of concept on 2026-05-05 (depthfirst, 2026-05-13); the earlier dates and the NDA had no source. VulnCheck reported exploitation attempts against its honeypots, with their purpose unknown (The Hacker News, 2026-05-17). The NGINX project rates the flaw medium (nginx.org), against the CVSS 4.0 score of 9.2 NCSC-CH gives (NCSC-CH Security Hub #12575, 2026-05-15).
F5's CVE description does not limit code execution to hosts with ASLR disabled. depthfirst's proof of concept runs with ASLR off, but depthfirst notes that forked NGINX workers share one heap layout, which could in theory be used to leak ASLR (depthfirst, 2026-05-13), and F5's CVE description, updated on 2026-09-10, covers systems with ASLR disabled or where the attacker can bypass ASLR (ENISA EUVD, 2026-09-10). An enabled ASLR is therefore no reason to defer the upgrade. Where the upgrade has to wait, depthfirst's workaround is to replace unnamed captures with named captures in every affected rewrite directive (depthfirst, NGINX Rift).