Nginx Gateway FabricWeb server / proxy · F5
CVE-2026-60005
Official description Straight from the sourceThe vendor's or NVD's own wording, published unedited. Authoritative, but often terse — it says what broke, rarely what to do.
NVD · uneditedNGINX 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.
In the news
Third-party coverageSurfaced from public web coverage — external links open in a new tab.
Technical summary Written by usOur analysis, written from the advisory, the CVSS vector and the affected-version data. It adds context the advisory leaves out, and never invents facts that are not in the source.
dbcve analysis · moderate confidenceThis vulnerability exists in the ngx_http_slice_module of NGINX. When the slice directive is used with unnamed regex captures in location blocks, or during background cache updates, unauthenticated remote attackers can trigger uninitialized memory access in the NGINX worker process. This leads to limited disclosure of heap/buffer memory contents or worker process restart (Denial of Service). The module is not enabled by default and requires explicit compilation with --with-http_slice_module.
Verify against the referenced sources before acting — the references below are authoritative for this CVE, this summary is not.
Affected products & versions What the vendor confirmedThe version ranges the vendor confirmed as vulnerable. If your version sits inside a range here, treat yourself as exposed until you have upgraded.
NVD · CPE data
Nginx Gateway FabricWeb server / proxy
>= 1.3.0, <= 1.6.2>= 2.0.0, < 2.6.7
Nginx Ingress ControllerWeb server / proxy
>= 3.5.0, <= 3.7.2>= 5.0.0, < 5.5.3>= 2026-lts-r1, < 2026-lts-r4= 4.0.0= 4.0.1
Nginx Instance ManagerWeb server / proxy
>= 2.17.0, < 2.22.2
Nginx Open SourceWeb server / proxy
>= 1.30.0, < 1.30.4= 1.31.2
Nginx PlusWeb server / proxy
>= 37.0.0.1, < 37.0.3.1>= r33, < r36= r36
WafApplication
>= 4.11.0, <= 4.16.0>= 5.2.0, <= 5.8.0>= 5.9.0, < 5.13.4CVSS breakdown How the score is builtThe industry scoring standard. It rates how the flaw is reached, what it takes to exploit, and what an attacker gains — the score is derived from those, not the other way round.
From the vector- Attack vector
- Network
- Complexity
- Low
- Privileges
- None
- User interaction
- None
- Scope
- Unchanged
- Confidentiality
- Low
- Integrity
- None
- Availability
- High
CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:H
Am I affected? How to checkSteps we derive from the advisory and the affected-version data, so you can decide whether this CVE reaches your setup. They are a guide, not a scan — your own configuration is the authority.
dbcve checksWork through these to decide whether this CVE applies to you.
-
Verify ngx_http_slice_module is compiled into NGINXRun 'nginx -V 2>&1 | grep -o http_slice_module' or check nginx binary for the slice moduleAffected if The output is empty (module not compiled) or shows the module (module is compiled)
-
Identify if the slice directive is in useSearch all NGINX config files for 'slice' keyword: 'grep -r "\bslice\b" /etc/nginx/' or check active configuration with 'nginx -T'Affected if No 'slice' directives found means the vulnerable code path is not exercised
-
Check for location blocks with regex captures using sliceReview all location ~ or location ~* blocks that contain the slice directive; look for unnamed capture groups like () without named identifiersAffected if Any location block with regex and unnamed captures uses the slice directive
-
Check for cache configurations with background updatesExamine proxy_cache_use_stale, fastcgi_cache_use_stale, or similar cache configurations that may trigger background updates when combined with slice directiveAffected if Cache with background update behavior is configured alongside slice directive
You are affected if ngx_http_slice_module is compiled into NGINX AND the slice directive is actively used in configuration, particularly in regex location blocks or with background cache updates.
Generated from the published advisory. Verify against your own configuration.
Remediation Closing itWhat it takes to close this. Where a vendor fix exists we point at it; where none exists we say so plainly, and can build one. Effort estimates are scoped from the advisory, not from your codebase.
dbcve · scoped1.30.42.6.72.22.2
If the ngx_http_slice_module is not required, ensure it is not compiled into NGINX. If enabled, audit all configurations using the slice directive to eliminate unnamed regex capture groups, and monitor for unexpected worker process restarts. Apply vendor patches when released.
Upgrade to the latest NGINX Plus or NGINX Open Source release that includes the fix for CVE-2026-60005 (check my.f5.com for exact version)
- Check if the NGINX http slice module is enabled by running 'nginx -V' and looking for '--with-http_slice_module' in the configure arguments
- If the slice module is not needed, rebuild NGINX without the --with-http_slice_module configuration parameter to eliminate the attack surface
- If the slice module is required, monitor my.f5.com for the official security advisory and patch release addressing CVE-2026-60005
- Once the patched version is released, upgrade NGINX to that fixed release
Generated from the published advisory — verify against the referenced sources before acting.
Fix this in Nginx Gateway Fabric
Scoped from the published advisory
- Consultation3.0 h
- Implementation2.0 h
- Testing2.0 h
- Review / QA2.0 h
An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $2,592.
Scan for this in your stack
Free · runs locallyCheck whether your project pulls in CVE-2026-60005 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.
References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.
Primary sourcesPractitioner notes
ContributedPeer-ranked notes from engineers who’ve handled CVE-2026-60005 in production — separate from our analysis above.
The advisory tells you what broke. It rarely tells you what actually worked. If you’ve dealt with this one, that detail is what the next engineer is searching for.
- The version that genuinely resolved it — not the one the vendor claimed
- A config change or rule that shut the vector down
- A gotcha in the upgrade path that cost you an afternoon
No notes yet
Be the first to add a field note for this CVE — a mitigation you’ve verified, a version caveat, or a link to a working fix. Sign in above to contribute.
A place for practitioners to share what actually worked: a mitigation you’ve tested, a configuration change, a version- or environment-specific caveat, or a link to a verified patch. The most useful notes rise to the top as peers upvote them, so the signal stays high.
- Verified mitigations, workarounds, and config changes
- Version or environment caveats, and links to real fixes
- No weaponised exploit code, or anything meant to cause harm
- No spam, self-promotion, credentials, or personal data