CTIPilot
AI-generated · no human review · verify critical claims against the linked source. how it works →

F5 WAF for NGINX

product · product:f5-waf-for-nginx

Coverage
1
first 2026-05-15 → last 2026-10-11
Latest activity
2026-05-15
CVE-2026-42945, NGINX Open Source / Plus / F5 WAF products: 18-year-old heap buffer overflow in rewrite…
Peak priority
high
1 high
Targets
·
no sector or region stated
Sources cited
7
6 hosts

Action items (1)

Do-now tasks recorded on the entries about F5 WAF for NGINX, newest first. Check the date before acting on an older one.

  • Audit NGINX configurations for the CVE-2026-42945 vulnerable pattern and either apply the workaround or upgrade. Grep all nginx.conf and included config files for rewrite directives combining an unnamed PCRE capture ($1, $2) with a replacement containing ? followed by another rewrite, if, or set in the same scope. Replace unnamed captures with named captures ((?<name>...) → $name) as an immediate workaround. Upgrade to NGINX Open Source 1.30.1 / 1.31.0 or NGINX Plus R32 P6 / R36 P4 to remediate. Check Kubernetes clusters for NGINX Ingress Controller version and apply the corresponding fixed chart. Prioritise internet-facing reverse proxies and API gateways.
    2026-05-15CVE-2026-42945

Defender insights

What each entry about F5 WAF for NGINX tells a defender to do, newest first.

2026-05-15HIGHCVE-2026-42945, NGINX Open Source / Plus / F5 WAF products: 18-year-old heap buffer overflow in rewrite module ("NGINX Rift"), PoC public

Exposure · detection

Story timeline

  1. 2026-05-15CVE-2026-42945, NGINX Open Source / Plus / F5 WAF products: 18-year-old heap buffer overflow in rewrite module ("NGINX Rift"), PoC public
    trending-vulnerabilities

Hunting pivots

Releases covered
F5 WAF for NGINX
ATT&CK techniques (1 across 1 tactic)

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 v19.2 · 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.

Evidence: 2026-05-15/cve-2026-42945-nginx-open-source-plus-f5-waf-products-18-yea · ATT&CK page ↗

Entries about F5 WAF for NGINX (1)

2026-05-15 · view entry permalink →

HIGHCVE-2026-42945updatedNATOA2

CVE-2026-42945, NGINX Open Source / Plus / F5 WAF products: 18-year-old heap buffer overflow in rewrite module ("NGINX Rift"), PoC public

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 +, %, and & by two bytes each) 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. Reliable impact is crash of the NGINX worker process (DoS with automatic master restart); RCE requires ASLR to be disabled on the host. 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).

Contradiction: the NGINX project rates the flaw severity medium (nginx.org), while NCSC-CH gives a CVSS 4.0 score of 9.2 (NCSC-CH Security Hub #12575, 2026-05-15) and depthfirst rates it critical at 9.2 (depthfirst, 2026-05-13); the gap likely reflects the preconditions, a specific rewrite pattern and, for code execution, ASLR disabled.

Correctionrun 2026-10-11T1307Z-auditsummarycvessourcesreferencestechniquesaffected_productsclassificationbodyevent_dateactions

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).

Builds on: SAP's August patch day is led by a CVSS 10.0 pre-auth code-execution flaw in the Commerce Cloud…

vulnerability15 May 05:00Zmulti-sourceOpen finding →

Co-occurring entities

Derived: referenced by the same focused operational entries (weekly summaries and report roundups don't count); ×N counts the shared entries.

Where this entity is cited

  • Vulns1

Source distribution

  • depthfirst.com2 (29%)
  • github.com1 (14%)
  • nginx.org1 (14%)
  • security-hub.ncsc.admin.ch1 (14%)
  • securityaffairs.com1 (14%)
  • thehackernews.com1 (14%)