Finding and attribution
A state mismatch after an incomplete upstream status-line read can produce an excessive cross-buffer length in SCGI/uWSGI response handling. The affected scgi_pass or uwsgi_pass configuration is required, along with an unauthenticated attacker able to intercept and control upstream-server responses. F5 says worker memory may be read or the worker restarted.
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-42946.
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-42946; 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 upstream NGINX Open Source fixed in 1.30.1 and 1.31.0 (and affected NGINX Plus branch fixes). 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: High · highest recorded score 8.3. Documented technical effects: data disclosure, 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-42946: CVSS 3.1 · 6.5 (Medium) ·
CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:L. F5 CNA CVE Program record · checked 17 Nov 2026. - CVE-2026-42946: CVSS 4.0 · 8.3 (High) ·
CVSS:4.0/AV:N/AC:L/AT:P/PR:N/UI:N/VC:H/VI:N/VA:L/SC:N/SI:N/SA:N. F5 CNA CVE Program record · checked 17 Nov 2026.
CVE-2026-42946: data disclosure, denial of service.
Prerequisites / affected scope: The affected scgi_pass or uwsgi_pass configuration is required, along with an unauthenticated attacker able to intercept and control upstream-server responses. F5 says worker memory may be read or the worker restarted..
Exploitation evidence: F5 says memory read or worker restart may result. The source does not establish arbitrary code execution or exploitation in the wild.. Impact source · checked 17 Nov 2026.
Documented fix: F5’s CNA lists upstream NGINX Open Source fixed in 1.30.1 and 1.31.0 (and affected NGINX Plus branch fixes). Distribution backports and deployment status are not inferred.