F5 NGINX Ingress Controller
NGINX Ingress Controller vulnerability
An authentication and authorization bypass vulnerability exists in F5 NGINX Kubernetes Ingress Controller (NIC) when configured with the `ExternalAuth` policy or Ingress external authentication. Client-supplied X-Forwarded-Prefix, X-Forwarded-URI, X-Original-URI, and X-Forwarded-Method routing and method headers are forwarded unsanitized into the internal authentication subrequest (handled by the NGINX auth_request directive). As a result, an unauthenticated, remote attacker may spoof request attributes evaluated by the external authentication provider. Impact: This vulnerability may allow remote attackers unauthenticated access to protected paths. There is no control plane exposure; this is a data plane issue only. Note: Software versions which have reached End of Technical Support (EoTS) are not evaluated.
Affected versions and mitigation
From the CVE record and the vendor's references.Affected
- >= 5.5.0, < 5.7.0
Fixed in 5.7.0
Mitigation
Upgrade NGINX Ingress Controller to 5.7.0 or later.
Workaround
Customers can configure their external authentication backend to ignore client-supplied `X-Forwarded-*` / `X-Original-*` headers or ensure it only evaluates session tokens rather than forwarded paths.
References
- Vendor advisory my.f5.com/manage/s/article/K000162611
Timeline
Days relative to CVE publicationNo public PoC found yet; not in CISA KEV.
PoC repositories
Found on GitHub.No PoC repositories found yet.