AI Science Tracker

NGINX rewrite/set capture heap buffer overflow

F5 NGINX Open Source and NGINX Plus · AI involvement attributed to depthfirst automated security analysis system (specific model not identified)

Finding and attribution

A rewrite replacement containing a question mark followed by a rewrite/if/set that uses an unnamed PCRE capture can leave the script engine’s argument-state flag set, so length calculation underallocates before a later copy. An unauthenticated remote client sends crafted HTTP requests to an affected NGINX configuration using the relevant rewrite/capture sequence. F5 says worker restart can result and code execution is possible when ASLR is disabled or bypassed; the researcher’s demonstrated RCE used ASLR off.

Product: F5 NGINX Open Source and NGINX Plus. AI system: depthfirst automated security analysis system (specific model not identified). Team / organization: depthfirst / F5 NGINX.

CVE identifiers: CVE-2026-42945.

AI and human contribution (source account): depthfirst’s primary NGINX Rift account says its system autonomously discovered four confirmed issues and individually identifies CVE-2026-42945; it says the system generated detailed root-cause reports and PoCs. F5’s CNA record credits the human researcher Zhenpeng (Leo) Lin for this specific finding and independently confirms the issue. The account does not identify the model used.

Human involvement is only described where the source account establishes it; unknown involvement does not mean none. Vendor confirmation of a flaw does not confirm every claim about AI contribution.

Discovery context: The F5 CNA record and depthfirst account give public disclosure date 2026-05-13/2026-05-13. The sources document a research PoC where applicable; they do not report exploitation in the wild or establish zero-day status.

Remediation status: fix documented. F5’s CNA lists NGINX Open Source fixed in 1.30.1 and 1.31.0 and affected NGINX Plus fixed in R36 P4 and R32 P6; root/research notes also track later module changes. Distribution backports and deployment status are not inferred.

A source-documented fix does not establish installed patches or current safety. Source checking does not independently reproduce the finding or establish observed exploitation.

Disclosed 13 May 2026. AI attribution dated 13 May 2026. Sources checked 17 Nov 2026; these are separate dates, not a live installation check.

Recorded CVSS: Critical · highest recorded score 9.2. Documented technical effects: code execution, denial of service.

Severity, consequences and exploitation evidence

Case grouping uses the highest recorded CVSS score, with its version-specific severity band. It is descriptive, not a combined or editorial risk index. All recorded assessments remain below; scores from different versions and sources may disagree. CVSS specifications define version-specific scoring and severity bands.

  • CVE-2026-42945: CVSS 3.1 · 8.1 (High) · CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H. F5 CNA CVE Program record · checked 17 Nov 2026.
  • CVE-2026-42945: CVSS 4.0 · 9.2 (Critical) · CVSS:4.0/AV:N/AC:H/AT:N/PR:N/UI:N/VC:H/VI:H/VA:H/SC:N/SI:N/SA:N. F5 CNA CVE Program record · checked 17 Nov 2026.

CVE-2026-42945: code execution, denial of service.
Prerequisites / affected scope: An unauthenticated remote client sends crafted HTTP requests to an affected NGINX configuration using the relevant rewrite/capture sequence. F5 says worker restart can result and code execution is possible when ASLR is disabled or bypassed; the researcher’s demonstrated RCE used ASLR off..
Exploitation evidence: F5’s CNA gives the conditional RCE boundary; depthfirst reports its working RCE PoC with ASLR off. Do not generalize code execution to ASLR-on conditions.. Impact source · checked 17 Nov 2026.

Documented fix: F5’s CNA lists NGINX Open Source fixed in 1.30.1 and 1.31.0 and affected NGINX Plus fixed in R36 P4 and R32 P6; root/research notes also track later module changes. Distribution backports and deployment status are not inferred.

Original evidence

Download this source record (JSON)

Open this case in the interactive tracker · Browse all static security cases