# CVE-2026-60005: NGINX ngx_http_slice_module vulnerability

> Unauthenticated attackers can trigger uninitialized memory access in NGINX, leading to limited memory disclosure or worker restarts when the slice module is enabled.

- **Severity:** High 8.8 (`CVSS:4.0/AV:N/AC:L/AT:N/PR:N/UI:N/VC:L/VI:N/VA:H/SC:N/SI:N/SA:N`)
- **Exploited in the wild:** Not known
- **Login needed:** Not needed
- **Attackable:** Over the internet
- **Victim action needed:** Not needed
- **Fix available:** Yes
- **Published:** 15 Jul 2026
- **Updated:** 15 Jul 2026
- **Also known as:** ALPINE-CVE-2026-60005, BELL-CVE-2026-60005, BIT-nginx-2026-60005, BIT-nginx-gateway-2026-60005, DEBIAN-CVE-2026-60005, ECHO-0dab-2681-8319, GHSA-vxcv-h5wj-jxr5, MINI-63r4-mmw4-rrwv, MINI-f398-f66f-9m9v, MINI-g655-x57g-24jp, MINI-q78p-7q64-gmq3, MINI-qc9x-6r43-cp2f, MINI-x8vh-28cq-6cv4, ROOT-OS-ALPINE-315-CVE-2026-60005, ROOT-OS-ALPINE-320-CVE-2026-60005, ROOT-OS-DEBIAN-11-CVE-2026-60005, UBUNTU-CVE-2026-60005

## What is CVE-2026-60005?

CVE-2026-60005 is a high-severity vulnerability in F5 NGINX Open Source, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.

### Official 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.

Weakness: CWE-908 (Use of Uninitialized Resource)

## Which versions are affected by CVE-2026-60005?

2 open source packages ship an affected version, including nginx and nginx-gateway. It affects 6 products.


| Package | Ecosystem | Affected | Fixed in |
| --- | --- | --- | --- |
| `nginx` | Bitnami | From 1.15.8 | 1.30.4, 1.31.3 |
| `nginx-gateway` | Bitnami | From 1.15.8 | 1.30.4, 1.31.3 |

Products: F5 Nginx Gateway Fabric, F5 Nginx Ingress Controller, F5 Nginx Instance Manager, F5 Nginx Open Source, F5 Nginx Plus, F5 Waf.

## How do I fix CVE-2026-60005?

Upgrade nginx to a fixed version for your release line: 1.30.4 or 1.31.3.

## Is CVE-2026-60005 being exploited?

There is no known exploitation of CVE-2026-60005 in the wild and no public exploit code.

## Other vulnerabilities in F5 NGINX Open Source

- [CVE-2026-42533](https://insights.sbomify.com/CVE-2026-42533/): NGINX Map directive and Regex matching vulnerability (critical 9.2)
- [CVE-2026-42530](https://insights.sbomify.com/CVE-2026-42530/): NGINX Open-Source ngx_http_v3_module vulnerability (critical 9.2)
- [CVE-2026-11311](https://insights.sbomify.com/CVE-2026-11311/): NGINX Gateway Fabric vulnerability (high 8.6)
- [CVE-2026-50107](https://insights.sbomify.com/CVE-2026-50107/): NGINX Gateway Fabric vulnerability (high 8.6)
- [CVE-2026-56434](https://insights.sbomify.com/CVE-2026-56434/): NGINX ngx_http_ssi_module vulnerability (high 8.3)

## Fix prompt for AI coding agents

```text
Check this codebase for CVE-2026-60005 and fix it if it is affected.

What it is: CVE-2026-60005 is a high-severity vulnerability in F5 NGINX Open Source, published on 15 Jul 2026. An attacker can exploit it over the internet without logging in, with no action from the victim.
Exploitation: There is no known exploitation of CVE-2026-60005 in the wild and no public exploit code.

Affected packages and fixed versions:
- nginx (Bitnami): affected from 1.15.8; fixed in 1.30.4, 1.31.3
- nginx-gateway (Bitnami): affected from 1.15.8; fixed in 1.30.4, 1.31.3

Task:
1. Search the dependency manifests and lockfiles (for example package.json, package-lock.json, requirements.txt, poetry.lock, uv.lock, pom.xml, build.gradle, go.mod, Cargo.lock, Gemfile.lock) and any Dockerfiles for the affected packages, including transitive dependencies.
2. If an affected version is in use, upgrade it to the fixed version for its release line with the project's package manager, so the lockfile is regenerated. Prefer the smallest upgrade that fixes it.
3. If there is no fix, or the upgrade would break the build, do not guess: explain the risk and the safest workaround instead.
4. Run the tests and summarise what changed and why.
5. If nothing in the project is affected, say so and change nothing.

Reference: https://insights.sbomify.com/CVE-2026-60005/ (Markdown: https://insights.sbomify.com/CVE-2026-60005/index.md)
```

## Sources

- CVE record: https://www.cve.org/CVERecord?id=CVE-2026-60005
- NVD: https://nvd.nist.gov/vuln/detail/CVE-2026-60005
- OSV: https://osv.dev/vulnerability/CVE-2026-60005

---
From sbomify Insights: https://insights.sbomify.com/CVE-2026-60005/
Summaries are generated and may contain mistakes; the official description above is the record.