CVE-2026-60005
NGINX ngx_http_slice_module memory disclosure and worker crash via crafted requests
Is CVE-2026-60005 being exploited?
Not confirmed. CVE-2026-60005 does not appear in CISA's Known Exploited Vulnerabilities catalog, which records only exploitation that has been observed and reported publicly. That is evidence of absence of a report, not evidence the flaw is unattacked. EPSS currently estimates a 0.71% probability of exploitation in the next 30 days.
How severe is CVE-2026-60005?
CVE-2026-60005 is rated High with a CVSS score of 8.8. Severity describes how bad exploitation would be, not how likely it is: pair it with exploitation evidence before deciding what to patch first.
Is there a patch for CVE-2026-60005?
Yes. A fix has been recorded for CVE-2026-60005. The vendor advisory is the authority on the exact fixed version — apply it from there rather than from a summary.
What does CVE-2026-60005 affect?
CVE-2026-60005 affects NGINX Open Source (built with --with-http_slice_module), NGINX Plus (http_slice module enabled). Confirm the exact affected versions against the vendor advisory before deciding you are exposed.
What should I do about CVE-2026-60005?
Disable http_slice module or apply vendor patch when released; monitor logs and restart workers after patch.
Exploitation status reflects CISA's KEV catalog as we last synced it. Check the catalog directly.
Unauthenticated remote attackers can cause limited memory disclosure or crash/restart NGINX worker via crafted requests to ngx_http_slice_module.
Patch when possible
- affected>= 1.31.2 and < 1.31.3
- affected>= 1.15.8 and < 1.30.4
- affected>= 37.0.0.1 and < 37.0.3.1
- affected>= R36 and < R36 P7
- affected>= R33 and < *
As published in the CVE Program record. A version outside these ranges is not a statement that it is unaffected — vendors sometimes understate a range, and distribution-backported builds carry upstream numbers that do not reflect what was patched into them.