CVE-2026-60005

NGINX ngx_http_slice_module vulnerability

HIGH
8.2
CVSS Score
Published: July 15, 2026 at 03:04 PM UTC
Updated: August 11, 2026 at 03:09 PM UTC
6 products affected across 1 vendorNGINX PlusNGINX Open SourceNGINX Ingress Controller

Using NGINX Plus by F5?

Get instant alerts when new vulnerabilities affect NGINX Plus - before attackers find them.

Real-time alertsTrack your software stackFree plan available
Severity
HIGH8.2
Exploit prediction
EPSS 0.5%
SSVC
No known exploit

Description

NGINX Plus and NGINX Open Source have a vulnerability in the ngx_http_slice_module module. When the slice directive and unnamed regex captures are configured or when a background cache update happens, unauthenticated attackers can send requests that may cause uninitialized memory access in the NGINX worker process, leading to limited disclosure of memory or a restart. Impact: This vulnerability may allow remote, unauthenticated attackers to have limited control to disclose memory contents or restart the NGINX worker process. There is no control plane exposure; this is a data plane issue only. Note: The ngx_http_slice_module module is not enabled by default; it's enabled with the --with-http_slice_module configuration parameter. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

Affected

Our own answer: ranges merged, affected separated from platform-only, with confidence and review flags.

1.3.0 ≤ v ≤ 1.6.22.0.0 ≤ v < 2.6.7
Affected range stops below 2.6.7, so it looks safe — our inference, not a vendor statement
2026-lts-r1 ≤ v < 2026-lts-r43.5.0 ≤ v ≤ 3.7.25.0.0 ≤ v < 5.5.34.0.04.0.1
Affected range stops below 2026-lts-r4, so it looks safe — our inference, not a vendor statement
Affected range stops below 5.5.3, so it looks safe — our inference, not a vendor statement
2.17.0 ≤ v < 2.22.2
Affected range stops below 2.22.2, so it looks safe — our inference, not a vendor statement
1.15.8 ≤ v < 1.30.41.30.0 ≤ v < 1.30.41.31.2 ≤ v < 1.31.31.15.81.31.2
Affected range stops below 1.30.4, so it looks safe — our inference, not a vendor statement
Affected range stops below 1.31.3, so it looks safe — our inference, not a vendor statement
v ≥ R3337.0.0.1 ≤ v < 37.0.3.1R36 ≤ v < R36 P7r33 ≤ v < r3637.0.0.1R33R36r36r36 p1r36 p2r36 p3r36 p4r36 p5r36 p6
Affected range stops below 37.0.3.1, so it looks safe — our inference, not a vendor statement
Affected range stops below R36 P7, so it looks safe — our inference, not a vendor statement
Affected range stops below r36, so it looks safe — our inference, not a vendor statement
4.11.0 ≤ v ≤ 4.16.05.2.0 ≤ v ≤ 5.8.05.9.0 ≤ v < 5.13.4
Affected range stops below 5.13.4, so it looks safe — our inference, not a vendor statement

Remediation

No guide yet

No remediation guidance has been written for this CVE yet. What the record does show:

References (1)

Vendor AdvisoryPatch
Source: cverecord
https://my.f5.com/manage/s/article/K000162100

SSVC — Action Prioritization

SSVCNo known exploitAutomatablePartial impact

SSVC signals action urgency (what to patch first), separate from CVSS which measures severity.

CVSS

8.2HIGHf5
Attack Vector
NETWORK
Complexity
LOW
Privileges
NONE
User Interaction
NONE
Scope
UNCHANGED
Confidentiality
LOW
Integrity
NONE
Availability
HIGH
Vector?

Quick Info

StatusANALYZED
CWE
CWE-908

Get alerted

Stop reading CVE feeds looking for your own stack

Track the products you run and VulnTracker tells you when a new CVE affects them — with what is known about fixing it, and nothing about the rest.

Free plan, no card