Quick answers
- Is CVE-2026-60005 exploited in the wild?
- No. Junglewise Threat Intelligence has no report of CVE-2026-60005 being exploited in the wild.
- How severe is CVE-2026-60005?
- High severity, with a CVSS score of 8.2, published 15 July 2026.
- Which products and versions are affected?
- F5 Nginx Plus 37.0.0.1 to 37.0.3.1, R36 before P7, R33 and later.
- Is there a fix for CVE-2026-60005?
- No fixed version is recorded yet. Check the vendor's advisory in the references below. If you run it, Junglewise drafts a mitigation that fits your setup and applies it once you approve, with senior security engineers behind it.
- How is CVE-2026-60005 attacked?
- It is attacked over the network, in a web application.
- Am I affected by CVE-2026-60005?
- Check whether you run F5 Nginx Plus at an affected version. Junglewise does that check for you around the clock: connect your code, cloud and domains, and it matches new vulnerabilities like this one against what you actually run and tells you when one reaches you.
Technical details
A vulnerability exists in the NGINX ngx_http_slice_module (CWE-908) when the 'slice' directive is used alongside unnamed regex captures or during background cache updates. An unauthenticated remote attacker can send specially crafted requests that trigger uninitialized memory access in the NGINX worker process. This can result in a denial-of-service (DoS) via worker process restart or limited information disclosure of memory contents. The vulnerability is only present if NGINX is compiled with the --with-http_slice_module parameter, as it is not enabled by default. Patches are available in updated versions of NGINX Plus and Open Source.
Affected products
- F5 NGINX Plus 37.0.0.1 to 37.0.3.1, R36 before P7, R33 and later
- F5 NGINX Open Source 1.15.8 to 1.30.4, 1.31.2 to 1.31.3
Timeline
- 2026-07-15: advisory: Initial publication of the advisory