dbcve.org
Nginx Gateway FabricWeb server / proxy · F5

CVE-2026-50107

HIGH · 8.1 CVSS v3.1 Published 2026-06-17
Fix available
A fix is available. Upgrade to 2.6.4 or later.
See remediation →
87/100
Remediation priority · High
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 Plus or NGINX Open Source is configured as the data plane for NGINX Gateway Fabric, an injection vulnerability exists in the NGINX configuration generator component of NGINX Gateway Fabric. User-supplied string values from the NginxProxy Custom Resource Definition (CRD) access log format setting are rendered directly into NGINX configuration templates without sanitization or escaping. An authenticated attacker with permission to create or modify these CRDs may craft values that inject arbitrary NGINX configuration directives. This is a control plane issue; there is no data plane exposure from the vulnerability trigger itself. 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 · high confidence

This is a configuration injection vulnerability in NGINX Gateway Fabric's configuration generator. When NginxProxy CRD access log format settings are specified, user-supplied values are directly injected into NGINX configuration templates without sanitization or escaping, allowing authenticated attackers with CRD modify permissions to inject arbitrary NGINX directives.

MitigationRestrict permissions to create/modify NginxProxy CRDs to trusted users only until a patch implementing proper input sanitization is applied to NGINX Gateway Fabric.

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:>= 2.3.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
High
Integrity
High
Availability
None

CVSS:3.1/AV:N/AC:L/PR:L/UI:N/S:U/C:H/I:H/A:N

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 NGINX Gateway Fabric version
    Run 'kubectl get pods -n <namespace> -o jsonpath="{.items[*].spec.containers[?(@.name==\"nginx-gateway\")].image}"' to find the nginx-gateway container image, then extract the version from the image tag
    Affected if The version is greater than or equal to 2.3.0 and less than 2.6.4
  2. Check for NginxProxy CRDs in the cluster
    Run 'kubectl get crd | grep -i nginxproxy' to see if NginxProxy custom resource definition exists
    Affected if NginxProxy CRD is present in the cluster
  3. List existing NginxProxy resources
    Run 'kubectl get nginxproxies -A' to retrieve all NginxProxy custom resources in all namespaces
    Affected if Any NginxProxy resources exist in the cluster
  4. Inspect access log format configuration
    Run 'kubectl get nginxproxies -A -o jsonpath="{.items[*].spec.accessLogFormat}"' or inspect individual NginxProxy resources with 'kubectl get nginxproxy <name> -n <namespace> -o yaml' to check for accessLogFormat or accessLogPath settings
    Affected if accessLogFormat field is explicitly configured with user-supplied values in any NginxProxy resource
  5. Verify CRD modify permissions
    Review RBAC policies: run 'kubectl auth can-i create nginxproxies' and 'kubectl auth can-i update nginxproxies' to check if untrusted users have modification rights to NginxProxy resources
    Affected if Untrusted or unauthenticated users have create/modify permissions on NginxProxy CRDs

You are affected if NGINX Gateway Fabric version is between 2.3.0 and 2.6.4 (exclusive) AND any NginxProxy resource has access log format settings explicitly configured with user-controlled values.

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 permissions to create/modify NginxProxy CRDs to trusted users only until a patch implementing proper input sanitization is applied to NGINX Gateway Fabric.

Recommended fix High confidence

Nginx Gateway Fabric 2.6.4 or later

  1. Identify the current version of Nginx Gateway Fabric deployed in your cluster using kubectl get pods -n <namespace> or your deployment manifests
  2. Upgrade Nginx Gateway Fabric to version 2.6.4 or later. For Kubernetes deployments, update the image tag in your deployment configuration (e.g., container.image: nginx/nginx-gateway-fabric:2.6.4 or newer)
  3. Apply the updated deployment configuration using kubectl apply -f <deployment-file.yaml>
  4. Verify the upgrade was successful by checking that new pods are running: kubectl get pods -n <namespace>
  5. Review NginxProxy CRD configurations to ensure no malicious access log format values were injected prior to the upgrade
Caveat Review the release notes for 2.6.4 for any breaking changes between your current version and the upgrade target

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-50107 — 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-50107 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