CVE-2026-11311: NGINX Gateway Fabric configuration directive injection via CRD fields
- Vendor
- F5
CVE-2026-11311 is a high-severity injection vulnerability in the NGINX configuration generator component of NGINX Gateway Fabric when NGINX Plus is configured as the data plane. The flaw arises because user-controlled string values from the NginxProxy Custom Resource Definition (CRD) serverTokens field and the AuthenticationFilter CRD extraAuthArgs field are rendered directly into generated NGINX configuration templates without proper sanitization or escaping. An authenticated attacker with permission to create or modify these CRDs can supply crafted values that inject arbitrary NGINX configuration directives into the generated configuration. The issue is described as a control-plane vulnerability; the trigger is through management-plane configuration rather than direct data-plane request handling.
Impact, mitigation & remediation
What it means and what to do now: patch path, interim mitigations, and the assume-compromise checklist.
Impact
What an attacker gets, and what they’ve been doing with it.
Successful exploitation allows an authenticated attacker to alter the generated NGINX configuration by injecting arbitrary directives. Reported consequences include exposure of sensitive data from the NGINX pod filesystem, proxying or redirecting traffic to attacker-controlled endpoints, unauthorized behavior within the Kubernetes environment, and denial of service if the injected configuration prevents NGINX from reloading or causes service instability.
Mitigation
If you can’t patch tonight, do this now.
If immediate patching is not possible, restrict who can create or modify the affected Custom Resources, specifically the NginxProxy serverTokens field and the AuthenticationFilter extraAuthArgs field. Limit CRD write access through Kubernetes RBAC, use admission policies or validation controls to reject unsafe values, and monitor for unexpected changes to generated NGINX configuration or reload failures. Avoid allowing untrusted or low-trust users to manage these CRDs until patched.
Remediation
Patch, then assume compromise.
Upgrade NGINX Gateway Fabric to a fixed vendor release. The provided content indicates affected versions include 2.0.0 through 2.6.3, with fixes available in 2.6.4. Remediation should also include correcting the configuration generator logic so that CRD-derived values are properly sanitized and escaped before being rendered into NGINX templates, and reviewing RBAC and admission controls governing modification of the affected CRDs.
Exploits
No public exploits tracked yet. Mallory keeps watching.
Affected products & vendors
Products and vendors Mallory has correlated with this vulnerability. Open in Mallory to drill down to specific CPE configurations and version ranges.
Frequently asked questions
- Is CVE-2026-11311 exploited in the wild?
- As of Sep 25, 2026, Mallory has no reports of CVE-2026-11311 being exploited in the wild. It is not listed in CISA KEV.
- Is there a public exploit for CVE-2026-11311?
- As of Sep 25, 2026, Mallory has found no public exploit for CVE-2026-11311.
- Is there a patch for CVE-2026-11311?
- Upgrade NGINX Gateway Fabric to a fixed vendor release. The provided content indicates affected versions include 2.0.0 through 2.6.3, with fixes available in 2.6.4.
- What products are affected by CVE-2026-11311?
- F5 Nginx Gateway Fabric.
- How severe is CVE-2026-11311?
- CVE-2026-11311 has a CVSS v4 score of 8.6 (High) and an EPSS score of 0.57% (48th percentile) as of Sep 25, 2026.
Recent activity
11 sources tracked across advisories, community write-ups, and news. New activity surfaces here as Mallory finds it.