NGINX Kubernetes Ingress Controller - CraftedSignal Threat Feedhttps://feed.craftedsignal.io/products/nginx-kubernetes-ingress-controller/Trending threats, MITRE ATT&CK coverage, and detection metadata. Fed continuously.Hugoenhello@craftedsignal.iohello@craftedsignal.ioWed, 14 Oct 2026 16:38:40 +0000https://feed.craftedsignal.io/favicon-32x32.pngCraftedSignal Threat Feedhttps://feed.craftedsignal.io/3232https://feed.craftedsignal.io/favicon.svgAuthentication Bypass in F5 NGINX Kubernetes Ingress Controllerhttps://feed.craftedsignal.io/briefs/2026-10-nginx-ingress-auth-bypass/Wed, 14 Oct 2026 16:38:40 +0000hello@craftedsignal.iohttps://feed.craftedsignal.io/briefs/2026-10-nginx-ingress-auth-bypass/An authentication and authorization bypass in F5 NGINX Kubernetes Ingress Controller (NIC) allows remote attackers to spoof request attributes and access protected paths by manipulating unsanitized X-Forwarded-* headers.F5 NGINX Kubernetes Ingress Controller (NIC) is vulnerable to an authentication and authorization bypass when configured with the ExternalAuth policy or Ingress external authentication. The vulnerability stems from the improper sanitization of client-supplied HTTP headers, specifically X-Forwarded-Prefix, X-Forwarded-URI, X-Original-URI, and X-Forwarded-Method. These headers are forwarded into the internal authentication subrequest handled by the NGINX auth_request directive. Because the ingress controller trusts these headers without sanitization, a remote, unauthenticated attacker can manipulate them to spoof request attributes evaluated by the external authentication provider. This flaw resides strictly in the data plane and does not expose the control plane, yet it permits unauthorized access to sensitive backend resources protected by the ingress controller.

Impact

The vulnerability allows unauthenticated remote attackers to bypass security constraints and gain access to protected paths managed by the affected Kubernetes Ingress Controller. This constitutes a significant security risk for organizations relying on NIC for traffic management and path-level access control, potentially leading to unauthorized data exposure or interaction with internal microservices that assume authentication has been successfully validated at the ingress layer.

Recommendation

  1. Inventory all ingress controller deployments to determine if the ExternalAuth policy or Ingress external authentication is active.
  2. Monitor ingress traffic for anomalous HTTP headers, particularly where X-Forwarded-* headers contain unexpected characters or values inconsistent with the request path.
  3. Consult the F5 security advisory to identify patched versions of NGINX Kubernetes Ingress Controller and perform upgrades in all affected clusters.
  4. Implement strict header validation at the application level or via service mesh sidecars as a compensating control while the ingress controller is being patched.
]]>highadvisoryvulnerabilityingresskubernetes