dbcve.org
Nginx Gateway FabricWeb server / proxy · F5

CVE-2026-32682

MEDIUM · 6.5 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 2.6.4 or later.
See remediation →
71/100
Remediation priority · Elevated
Remotely reachable Zero-click

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 · unedited
When NGINX Gateway Fabric is configured using GRPCRoutes, an authenticated, remote attacker with permission to create or modify GRPCRoute resources can cause the NGINX Gateway Fabric control plane to terminate by sending undisclosed GRPCRoute configurations containing backendRef filters. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.

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 confidence

NGINX Gateway Fabric contains a denial-of-service vulnerability in its control plane when processing GRPCRoutes with backendRef filters. An authenticated attacker with permissions to create or modify GRPCRoute resources can send specially crafted configurations that cause the control plane to terminate unexpectedly.

MitigationRestrict GRPCRoute resource creation and modification permissions via Kubernetes RBAC policies until the vendor patch is applied; monitor for unauthorized GRPCRoute modifications.

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
Affected:>= 1.3.0, <= 1.6.2>= 2.0.0, < 2.6.4

CVSS 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
Low
User interaction
None
Scope
Unchanged
Confidentiality
None
Integrity
None
Availability
High

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:N/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 checks

Work through these to decide whether this CVE applies to you.

  1. Identify installed Nginx Gateway Fabric version
    Run 'kubectl get deployment -A -o jsonpath="{range .items[*]}{.metadata.namespace}{'\t'}{.metadata.name}{'\t'}{.spec.template.spec.containers[?(@.name=="nginx-gateway")].image}{'\n'}{end}"' to find the deployed image tags, then extract the version number from the image tag.
    Affected if The version falls within 1.3.0 to 1.6.2 (inclusive) or 2.0.0 to 2.6.3 (inclusive)
  2. Check if GRPCRoute resources exist
    Run 'kubectl get grpcroutes -A' to list any GRPCRoute resources in the cluster.
    Affected if GRPCRoute resources exist in the cluster and the Nginx Gateway Fabric version is affected
  3. Inspect GRPCRoutes for backendRef filters
    Run 'kubectl get grpcroutes -A -o yaml' to examine the full configuration of each GRPCRoute, specifically looking for 'backendRef' entries within the 'rules' section of the spec.
    Affected if Any GRPCRoute contains a backendRef filter configuration and the Nginx Gateway Fabric version is affected
  4. Verify control plane pod stability
    Run 'kubectl get pods -n <nginx-gateway-namespace> -o wide' to check pod status, then 'kubectl logs -n <nginx-gateway-namespace> <nginx-gateway-pod> --previous' to examine logs from any crashed containers.
    Affected if The control plane pods show frequent restarts, crash loops, or unexpected terminations after GRPCRoute creation or modification events
  5. Check RBAC permissions for GRPCRoute resources
    Run 'kubectl auth can-i create grpcroutes --as=<your-user>' or review existing ClusterRole/Role bindings to determine who has permissions to create or modify GRPCRoute resources.
    Affected if Users or service accounts other than intended administrators have create or update permissions on GRPCRoute resources

Your environment is affected if Nginx Gateway Fabric is deployed at a version between 1.3.0-1.6.2 or 2.0.0-2.6.3, and GRPCRoute resources with backendRef filters can be created or modified by unauthorized users, potentially causing control plane pod crashes.

Generated from the published advisory. Verify against your own configuration.

Check your environment

Paste your version and any relevant configuration and it will be compared against the affected criteria above. Do not include secrets or credentials.

AI-assisted, checked against the advisory. Informational, not a guarantee.

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 · scoped
Upgrade available Upgrade to 2.6.4 or later
Fixed in 2.6.4
Interim mitigation

Restrict GRPCRoute resource creation and modification permissions via Kubernetes RBAC policies until the vendor patch is applied; monitor for unauthorized GRPCRoute modifications.

Recommended fix High confidence

2.6.4 or later (for 2.x line); for 1.x users, migrate to 2.6.4+ on 2.x line

  1. Identify your current NGINX Gateway Fabric version using 'kubectl get pods -A | grep nginx-gateway' or checking your deployment manifests
  2. Determine if you are on the 1.x or 2.x release line based on your current version
  3. For versions 1.3.0 through 1.6.2: Upgrade to the 2.x release line (2.6.4 or later) since 1.x has reached EoTS
  4. For versions 2.0.0 through 2.6.3: Upgrade to version 2.6.4 or later
  5. Apply the upgrade using your Kubernetes deployment method (e.g., Helm upgrade, kubectl apply)
  6. Verify the upgrade was successful by checking pod status and ensuring NGINX Gateway Fabric is running the new version
  7. Monitor the control plane for stability after the upgrade
Caveat Upgrading from 1.x to 2.x may have breaking changes - review NGINX Gateway Fabric 2.x release notes for API and configuration changes before upgrading

Generated from the published advisory — verify against the referenced sources before acting.

Fix this in Nginx Gateway Fabric Scoped from the published advisory
  • Consultation4.0 h
  • Implementation8.0 h
  • Testing6.0 h
  • Review / QA4.0 h
22.0 hours of engineering $3,860
Get the upgrade done

An estimate, not a bill — we confirm scope with you before any work starts. Need it this week? Rush from $6,176.

Scan for this in your stack

Free · runs locally
dbcve dependency scanner

Check whether your project pulls in CVE-2026-32682 — or any other known-vulnerable package — straight from your lock files. Free and open source; it runs locally and uploads nothing.

Get it on GitHub Scan in the browser

References Go to the primary sourcePrimary sources — vendor advisories, patches and trackers. Where our summary and a reference disagree, the reference wins.

Primary sources

Practitioner notes

Contributed

Peer-ranked notes from engineers who’ve handled CVE-2026-32682 in production — separate from our analysis above.

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.

What this is

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.

What belongs here
  • 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