Ingress-NGINX Fixes CVE-2026-3288 Configuration Injection Flaw

Summary
Sysdig TRT explains how a quote in an Ingress path could inject nginx directives in vulnerable ingress-nginx versions, potentially enabling code execution or secret disclosure, and details fixes, exploitation conditions, and Falco detection.
Key points
- CVE-2026-3288 stems from missing path sanitization in buildProxyPass(); a quote in an Ingress path can inject nginx directives.
- Exploitation requires permission to create or modify Ingress resources in a cluster running a vulnerable NGINX Ingress Controller.
- The advisory says the flaw can enable remote code execution or disclosure of secrets accessible to the controller; Sysdig TRT also tested response hijacking, token exposure, internal IP disclosure, and denial of service.
- Versions before v1.13.8, v1.14.4, and v1.15.0 are listed as affected; those releases include the fix. The issue followed an earlier related fix for CVE-2026-24512.
- Sysdig TRT reports that the DeepInspect blocklist misses directives including return, set, and try_files, and that a path-validation regex is unused.
- A Falco rule can detect successful Ingress create or update operations with a quote in the path by inspecting Kubernetes audit logs; testing alerted on the exploit Ingress but not a benign test path.
- Recommendations include upgrading, restricting Ingress permissions, deploying the detection rule, and checking that the admission webhook is enabled.
Article Details
- Vulnerability Types
- Configuration injection via an Ingress path
- Path injection
- Severity
- CVSS 8.8 (HIGH)
- Affected Versions
- NGINX Ingress Controller versions before v1.13.8
- NGINX Ingress Controller versions before v1.14.4
- NGINX Ingress Controller versions before v1.15.0
- Exploitation Status
- unknown
- Exploit Availability
- unknown
- Patch Status
- available
- Workarounds
- Restrict permissions to create or modify Ingress resources using RBAC.
- Enable the ingress-nginx admission webhook; it rejects invalid generated nginx configurations, although valid-syntax payloads may pass.
CVE
CVE-2026-24512Kubernetes · ingress-nginxThe flaw resulted from a missed sanitization in buildProxyPass() after a prior fix for CVE-2026-24512, can lead to RCE and secret disclosure, and Sysdig TRT published analysis plus a Falco rule to detect Ingress pathsCVE-2026-3288Kubernetes · ingress-nginxOn March 9, 2026 the ingress-nginx project merged a fix for CVE-2026-3288, a configuration injection vulnerability in the NGINX Ingress Controller that allowed any user with permission to create or modify Ingress
Vendors
Products
KubernetesDetection and mitigation: Sysdig added threat intel and a Falco rule that watches Kubernetes audit logs for Ingress path values containing a double-quote; recommendations include patching, deploying the Falco rule,NGINX Ingress Controllerproject merged a fix for CVE-2026-3288, a configuration injection vulnerability in the NGINX Ingress Controller that allowed any user with permission to create or modify Ingress resources to inject arbitrarySysdig SecureDetection of this vulnerability has been added to the Sysdig Secure Threat Intelligence page, accessible at Home -> Threat Intelligence or by searching for “Remote Code Execution Vulnerabilities in NGINX Ingress
